ファイルカテゴリを管理します
AI agents use manage_categories to create or update resources in Claude MCP Server Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP Server Integration environment.
This tool modifies file categories/metadata, which is a reversible write operation. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute). The medium severity reflects that category mismanagement could cause organizational confusion or loss of file classification, but the effects are reversible and typically non-critical to system integrity.
From the tool's definition Tool name 'manage_categories' combined with description indicating file category management ('ファイルカテゴリを管理します' = 'manages file categories'). Management functions typically create, update, or modify metadata associated with files.
Attacks that exploit this kind of access
ファイルカテゴリを管理します. It is categorised as a Write tool in the Claude MCP Server Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for manage_categories: 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 Claude MCP Server Integration. Nothing to install.
manage_categories 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 manage_categories 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 manage_categories. 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.
manage_categories is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →