Execute card creation after user confirms
AI agents use apply_create_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 performs a reversible Write operation—creating new cards. While the server has destructive delete operations (delete_card, delete_deck), this tool specifically creates data. The 'two-phase commits and typed confirmations' mentioned in the server description indicate safety mechanisms are in place.
From the tool's definition Tool creates new flashcards in Mochi.cards after confirmation. The description indicates it 'Execute[s] card creation', and this is a create operation that modifies the flashcard database by adding new data.
Attacks that exploit this kind of access
Execute card creation after user confirms. 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_create_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.
apply_create_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 apply_create_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 apply_create_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.
apply_create_card 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 →