AI agents use create_tag to create or update resources in SP-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SP-MCP environment.
This tool creates new tag objects, which is a reversible write operation. It does not execute code, delete data, move money, or have destructive effects. Creating tags is a normal task management operation with minimal blast radius if misused by an AI agent—the worst case being unused or numerous tags cluttering the system, which is easily remediated.
From the tool's definition Tool name 'create_tag' and description 'Create a new tag' indicate data creation. Tags are metadata for task organization in Super Productivity, a task management system.
Documented attack patterns abuse exactly the kind of access create_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SP-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_tag:
{
"version": "1",
"default": "deny",
"tools": {
"create_tag": {
"limits": [
{
"counter": "create_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_tag 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 tag. It is categorised as a Write tool in the SP-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SP- MCP server in PolicyLayer and add a rule for create_tag: 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 SP-MCP. Nothing to install.
create_tag 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_tag 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_tag. 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_tag is provided by the SP- MCP server (organicmoron/sp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 SP-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 SP-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.