Find entities by NAME within a campaign — fast, server-side, but matches names only (no entry/body text). Prefer this when you know the entity name. For matching against entry text, use kanka_full_text_search instead. For listing/browsing, use kanka_list_entities.
AI agents call kanka_search to retrieve information from Kanka without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation that retrieves data without side effects. It does not create, modify, delete, execute code, or commit financial transactions. The fast, server-side name-based search is a classic Read operation with minimal security risk when properly scoped to campaign context.
From the tool's definition Tool description states it 'Find[s] entities by NAME within a campaign' and explicitly distinguishes itself from full-text search, indicating a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Find entities by NAME within a campaign — fast, server-side, but matches names only (no entry/body text). Prefer this when you know the entity name. For matching against entry text, use kanka_full_text_search instead. For listing/browsing, use kanka_list_entities. It is categorised as a Read tool in the Kanka MCP Server, which means it retrieves data without modifying state.
Register the Kanka MCP server in PolicyLayer and add a rule for kanka_search: 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 Kanka. Nothing to install.
kanka_search 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 kanka_search 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 kanka_search. 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.
kanka_search is provided by the Kanka MCP server (torinvdb/kanka-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 →