AI agents use create-category to create or update resources in PI API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PI API MCP Server environment.
This tool creates new data in the PI Dashboard system. Creation operations are classified as Write because they modify state reversibly—categories can be subsequently deleted or modified. The severity is medium because misuse could clutter the dashboard or create unwanted organizational structures, but the impact is localized and undoable.
From the tool's definition Tool name 'create-category' and description 'Create a new category' indicate data creation that is reversible (the category can be deleted via the sibling 'delete-category' tool).
Documented attack patterns abuse exactly the kind of access create-category gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PI API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-category:
{
"version": "1",
"default": "deny",
"tools": {
"create-category": {
"limits": [
{
"counter": "create-category_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create-category 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 category. It is categorised as a Write tool in the PI API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PI API MCP Server MCP server in PolicyLayer and add a rule for create-category: 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 PI API MCP Server. Nothing to install.
create-category 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-category 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-category. 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-category is provided by the PI API MCP Server MCP server (mingzilla/pi-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PI API 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.
18 PI API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.