This record as markdown: /tools/io-github-arielbk-anki-mcp/load-profile.md
What load_profile does on Anki
AI agents call load_profile to retrieve information from Anki without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why load_profile is rated Low
The name 'load_profile' is most consistent with a Read operation—fetching or retrieving profile data. With an empty description, confidence is reduced. No evidence of side effects, data modification, destructive actions, or financial operations. Severity is low as profile retrieval in a flashcard system poses minimal risk even if misused.
From the tool's definition Tool name 'load_profile' suggests retrieving/loading a profile configuration or state. Description is empty, limiting evidence precision.
Attacks that exploit this kind of access
The rule that runs load_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Anki, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For load_profile, this is the rule to start with:
load_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every load_profile call is checked against it from then on.
Questions about load_profile
load_profile is a read tool on the Anki MCP server. It is categorised as a Read tool in the Anki MCP Server, which means it retrieves data without modifying state.
Register the Anki MCP server in PolicyLayer and add a rule for load_profile: 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 Anki. Nothing to install.
load_profile 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 load_profile 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 load_profile. 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.
load_profile is provided by the Anki MCP server (@arielbk/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Anki, and thousands of servers like it.
This server
Across the catalogue