AI agents call kanka_describe_entity_type 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 merely queries and returns structural metadata about entity types—their schemas. It enables discovery of field requirements before write operations but performs no mutations itself. The sibling tools kanka_create_entity and kanka_delete_entity handle writes and deletes; this tool is purely advisory/informational, making it a Read action.
From the tool's definition Tool returns JSON Schema for entity type payloads; explicitly stated as informational discovery call ('Call this before kanka_create_entity or kanka_update_entity to discover required and optional fields').
Attacks that exploit this kind of access
Return the JSON Schema for the create/update payload of a Kanka entity type. Call this before kanka_create_entity or kanka_update_entity to discover required and optional fields. 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_describe_entity_type: 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_describe_entity_type 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_describe_entity_type 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_describe_entity_type. 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_describe_entity_type 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 →