Update an existing card
AI agents use update_card 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 flashcard data within the Mochi Cards system but does not permanently delete or destroy data (ruling out Destructive), does not execute arbitrary code or external operations (ruling out Execute), and does not involve financial transactions (ruling out Financial).
From the tool's definition Tool description states 'Update an existing card', which modifies existing data in a reversible manner. The tool name 'update_card' and description align with Write category behavior (create, update, post, upload).
Attacks that exploit this kind of access
Update an existing card. 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 update_card: 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.
update_card 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 update_card 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 update_card. 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.
update_card is provided by the Mochi MCP Server MCP server (shunkus/mochi-mcp-server). 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 →