Disconnects related entries from a relation field.
AI agents use disconnect_relation to create or update resources in Strapi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Strapi MCP Server environment.
This tool modifies relational data by removing connections between entries. Although it affects data structure, the operation is reversible (relations can be re-established), and the entries themselves are not deleted. This qualifies as Write rather than Destructive.
From the tool's definition Tool description states it 'Disconnects related entries from a relation field' — a modification operation that severs data relationships.
Documented attack patterns abuse exactly the kind of access disconnect_relation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Strapi MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for disconnect_relation:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect_relation": {
"limits": [
{
"counter": "disconnect_relation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disconnect_relation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnects related entries from a relation field. It is categorised as a Write tool in the Strapi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Strapi MCP Server MCP server in PolicyLayer and add a rule for disconnect_relation: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Strapi MCP Server. Nothing to install.
disconnect_relation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect_relation rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for disconnect_relation. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
disconnect_relation is provided by the Strapi MCP Server MCP server (l33tdawg/strapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Strapi MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Strapi MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.