AI agents use createSubtask to create or update resources in MCP Server Generator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server Generator environment.
The tool creates or modifies data (a new subtask) in a reversible manner. This is a Write operation rather than Read (it changes state), Execute (it doesn't run arbitrary code), or Destructive (subtasks can be deleted/modified). Severity is medium because misuse could create unnecessary clutter or disrupt project management workflows, but changes are reversible.
From the tool's definition Tool name 'createSubtask' indicates creation of a work item (subtask). No description provided to confirm exact behavior, but based on server context (manages MCP servers and work items like assignIssue, addIssueToSprint) this creates new data structures.
Documented attack patterns abuse exactly the kind of access createSubtask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Generator, and nothing reaches the server without passing your rules. This is the rule we recommend for createSubtask:
{
"version": "1",
"default": "deny",
"tools": {
"createSubtask": {
"limits": [
{
"counter": "createsubtask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createSubtask 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.
createSubtask. It is categorised as a Write tool in the MCP Server Generator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server Generator MCP server in PolicyLayer and add a rule for createSubtask: 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 MCP Server Generator. Nothing to install.
createSubtask 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 createSubtask 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 createSubtask. 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.
createSubtask is provided by the MCP Server Generator MCP server (serhatuzbas/mcp-server-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server Generator, 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.
79 MCP Server Generator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.