# Could I implement a new script engine in my plugin but limit the access only in the plugin

**URL:** <https://discuss.elastic.co/t/could-i-implement-a-new-script-engine-in-my-plugin-but-limit-the-access-only-in-the-plugin/379930>\
**Category:** Elasticsearch\
**Created:** [July 9, 2025, 3:33am UTC](https://discuss.elastic.co/t/could-i-implement-a-new-script-engine-in-my-plugin-but-limit-the-access-only-in-the-plugin/379930 "2025-07-09T03:33:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gaobinlong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gaobinlong/32/49319_2.png) [@gaobinlong](https://discuss.elastic.co/u/gaobinlong)\
**Post date:** [July 9, 2025, 3:33am UTC](https://discuss.elastic.co/t/could-i-implement-a-new-script-engine-in-my-plugin-but-limit-the-access-only-in-the-plugin/379930/1 "2025-07-09T03:33:02Z")

</div>

I have a custom plugin with a custom script engine, how could I limit the access scope of the script engine only in my plugin? How to make other plugins in Elasticsearch not able to submit the new type of script?