导出指定卡组
AI agents call anki_export_deck to retrieve information from TalkToAnki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a deck is a read/extraction operation — it reads and packages existing deck data for output without modifying or deleting anything in Anki. The description '导出指定卡组' means 'export specified deck', which is a non-destructive retrieval action.
From the tool's definition anki_export_deck / 导出指定卡组 ('export specified deck')
Attacks that exploit this kind of access
导出指定卡组. It is categorised as a Read tool in the TalkToAnki MCP Server, which means it retrieves data without modifying state.
Register the TalkToAnki MCP server in PolicyLayer and add a rule for anki_export_deck: 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 TalkToAnki. Nothing to install.
anki_export_deck is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the anki_export_deck 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 anki_export_deck. 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.
anki_export_deck is provided by the TalkToAnki MCP server (muxuuu/talktoanki). 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 →