Get identity headers for your own HTTP requests. Returns a Kya-Token header you can attach to requests made through Playwright, browser extensions, or any HTTP client you control. Call kya_getAgentIdentity first to establish your identity. Then pass these headers to page.setExtraHTTPHeaders() for...
AI agents call kya_getHeaders to retrieve information from Payclaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While the tool retrieves credentials rather than modifying data, it operates in a financial/commerce context (evidenced by sibling tools like kya_reportPurchase, kya_getCard, and the server's stated purpose of 'tokenized user identity and virtual Visa cards').
From the tool's definition Tool returns identity headers (Kya-Token) for HTTP requests. Description states it 'Returns a Kya-Token header you can attach to requests' and is used to 'establish your identity.' This is fundamentally a data retrieval operation that provides authentication…
Attacks that exploit this kind of access
Get identity headers for your own HTTP requests. Returns a Kya-Token header you can attach to requests made through Playwright, browser extensions, or any HTTP client you control. Call kya_getAgentIdentity first to establish your identity. Then pass these headers to page.setExtraHTTPHeaders() for browser automation, or set as a cookie via document.cookie for Chrome extensions. It is categorised as a Read tool in the Payclaw MCP Server, which means it retrieves data without modifying state.
Register the Payclaw MCP server in PolicyLayer and add a rule for kya_getHeaders: 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 Payclaw. Nothing to install.
kya_getHeaders 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_getHeaders 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_getHeaders. 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_getHeaders is provided by the Payclaw MCP server (kyalabs-io/mcp-server). 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 →