cardsInfo

THE RISK

Low Risk

Why cardsInfo needs a policy

This tool retrieves card metadata and information without creating, modifying, deleting, or executing any operations. It is purely informational, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'cardsInfo' and description 'Returns a list of objects containing information for each card ID provided' indicate a query/retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access cardsInfo gives an agent:

POLICY

How to control cardsInfo

PolicyLayer is an MCP gateway — it sits between your AI agents and Anki, and nothing reaches the server without passing your rules. This is the rule we recommend for cardsInfo:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cardsInfo": {}
  }
}

cardsInfo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Anki — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Anki tools

Destructive deleteDecks Deletes decks with the given names. The Destructive deleteMediaFile Deletes the specified file from Anki Destructive deleteNotes Deletes notes with the given IDs. Destructive modelFieldRemove Removes a field from an existing model. Write removeTags Removes tags from the specified notes. Write changeDeck Moves cards with the given IDs to a different deck, creating the deck if it doesn Write storeMediaFile Stores a media file in Anki Write unsuspend Unsuspends the specified cards. Returns true on success.

All 40 Anki tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cardsInfo

What does the cardsInfo tool do? +

Returns a list of objects containing information for each card ID provided. It is categorised as a Read tool in the Anki MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cardsInfo? +

Register the Anki MCP server in PolicyLayer and add a rule for cardsInfo: 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.

What risk level is cardsInfo? +

cardsInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cardsInfo? +

Yes. Add a rate_limit block to the cardsInfo 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.

How do I block cardsInfo completely? +

Set action: deny in the PolicyLayer policy for cardsInfo. 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.

What MCP server provides cardsInfo? +

cardsInfo is provided by the Anki MCP server (ujisati/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Anki tool call.

Start from Anki, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →