Verify a KYA identity card — check structure, completeness, and signature.
AI agents call kya_verify_card to retrieve information from Agent Safety without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs cryptographic verification and structural validation of identity card data. It has no side effects, does not modify state, and does not execute arbitrary code or delete data. It is purely informational—checking whether a card's signature is valid and its fields are complete. Even if verification fails, no action is taken on the card itself. This is a classic Read-category operation.
From the tool's definition Tool name 'kya_verify_card' and description 'Verify a KYA identity card — check structure, completeness, and signature' indicate read-only validation logic.
Attacks that exploit this kind of access
Verify a KYA identity card — check structure, completeness, and signature. It is categorised as a Read tool in the Agent Safety MCP Server, which means it retrieves data without modifying state.
Register the Agent Safety MCP server in PolicyLayer and add a rule for kya_verify_card: 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 Agent Safety. Nothing to install.
kya_verify_card 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 kya_verify_card 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 kya_verify_card. 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.
kya_verify_card is provided by the Agent Safety MCP server (luciferforge/agent-safety-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 →