AI agents call kanka_full_text_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 retrieves and searches existing campaign entity data without side effects. While it consumes API budget, that is a resource cost rather than a security impact. The operation is read-only and reversible. It does not create, modify, delete, or execute code — it simply queries and filters existing data. The primary risk is over-querying, which is mitigated by the server's instruction to 'narrow' searches.
From the tool's definition Tool performs 'Search across the body text of entities' with 'matching locally' — no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Search across the body text (entry HTML) of entities by paginating typed list endpoints, stripping HTML, and matching locally. Costs API budget — narrow. 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_full_text_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_full_text_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_full_text_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_full_text_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_full_text_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 →