Apply tag changes after user confirms. Use with token from add_tags_preview or remove_tags_preview.
AI agents use apply_tags_update to create or update resources in Mochi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mochi MCP Server environment.
This tool modifies existing data (card tags) in a reversible manner. While tags can be re-applied or removed again, the operation itself changes card state. The two-phase commit pattern (preview followed by apply) reduces risk but does not eliminate it.
From the tool's definition Tool description states it applies tag changes after user confirmation, indicating it modifies card metadata. It works with tokens from preview operations (add_tags_preview, remove_tags_preview), showing a write operation on flashcard tags.
Attacks that exploit this kind of access
Apply tag changes after user confirms. Use with token from add_tags_preview or remove_tags_preview. It is categorised as a Write tool in the Mochi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mochi MCP Server MCP server in PolicyLayer and add a rule for apply_tags_update: 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 Mochi MCP Server. Nothing to install.
apply_tags_update 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 apply_tags_update 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 apply_tags_update. 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.
apply_tags_update is provided by the Mochi MCP Server MCP server (nz99/mochi-mcp). 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 →