AI agents use create_component 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 creates new structural elements (components) in a Strapi CMS, which is a write operation that modifies the system's data model. While the action is reversible (components can be deleted), it alters the CMS schema and could affect the system's integrity if misused. It is Write rather than Execute because it directly creates data structures rather than executing arbitrary code.
From the tool's definition Tool name 'create_component' and description 'Create a new component' indicate irreversible data creation in a CMS structure.
Documented attack patterns abuse exactly the kind of access create_component 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 create_component:
{
"version": "1",
"default": "deny",
"tools": {
"create_component": {
"limits": [
{
"counter": "create_component_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_component 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.
Create a new component. 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 create_component: 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.
create_component 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 create_component 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 create_component. 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.
create_component 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.