タグの整理(リネーム、削除など)を行います
AI agents use organize_tags 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.
The description mentions both renaming and deleting tags. Renaming is a Write operation, while deletion could be Destructive. However, tag deletion is typically a metadata-level operation that may be reversible depending on implementation. Given the ambiguity and that tags are lightweight metadata rather than primary data, Write is the most appropriate category, though the deletion aspect raises severity to medium.
From the tool's definition タグの整理(リネーム、削除など)を行います — 'リネーム' (rename) and '削除' (delete) of tags
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 organize_tags: 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.
organize_tags 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 organize_tags 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 organize_tags. 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.
organize_tags 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 →