# Cursor Subagent MCP Toolset Control Request

**URL:** <https://forum.cursor.com/t/cursor-subagent-mcp-toolset-control-request/159786>\
**Category:** Feature Requests\
**Tags:** mcp, subagents, security\
**Created:** [May 5, 2026, 1:12pm UTC](https://forum.cursor.com/t/cursor-subagent-mcp-toolset-control-request/159786 "2026-05-05T13:12:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [May 7, 2026, 11:35am UTC](https://forum.cursor.com/t/cursor-subagent-mcp-toolset-control-request/159786/4 "2026-05-07T11:35:21Z")

</div>

Hey, thanks for the detailed feature request and the syntax example. That’s really helpful.

Confirming the current behavior: custom subagents inherit all MCP tools from the parent, and the only way to restrict it is the `readonly` flag, which blocks MCP entirely with no per-tool control. Per-server or per-tool whitelisting via frontmatter isn’t supported right now.

We’re aware of the gap, and we’re discussing the spec internally, but I can’t share a concrete timeline or the final config format yet. I’ll pass along your example with an `mcp_servers` block and a tool-level array as a clear signal. The use case is easy to see and helps with prioritization, especially for token efficiency and read-only safety.

A couple related threads if you want to follow along:

- [Subagent control via rules and settings](https://forum.cursor.com/t/159562)
- [Workspace- or profile-scoped Cursor config (rules, skills, subagents, MCP)](https://forum.cursor.com/t/153068)

If there’s an update on the design, I’ll post it here.

---

_[View the full topic](https://forum.cursor.com/t/cursor-subagent-mcp-toolset-control-request/159786)._
