# Instructions for limiting behavior in custom commands is confusing

**URL:** <https://forum.cursor.com/t/instructions-for-limiting-behavior-in-custom-commands-is-confusing/145188>\
**Category:** Feedback\
**Created:** [December 4, 2025, 1:14am UTC](https://forum.cursor.com/t/instructions-for-limiting-behavior-in-custom-commands-is-confusing/145188 "2025-12-04T01:14:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cerdman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/cerdman/32/61427_2.png) [@cerdman](https://forum.cursor.com/u/cerdman)\
**Post date:** [December 4, 2025, 1:14am UTC](https://forum.cursor.com/t/instructions-for-limiting-behavior-in-custom-commands-is-confusing/145188/1 "2025-12-04T01:14:03Z")

</div>

With custom modes deprecated, it would be helpful to provide examples of explicitly how to tell a Custom Commond what it can and cannot do, and provide some evidence of how those instructions will be respected (e.g. an internal whitelisting process etc.).

For instance, if I say “Use playwright-mcp-extension - and no other MCP tools” will that then break some internal Cursor tools that might ordinarily work, or will it know I am referring only to MCPs that I have configured?

If I say “Edit only files in foo/, not in bar/” will it 100% respect those instructions?

The current chat agent does not respect instructions like these ordinarily - so I am inclined to ask.

Thanks!