Retrieve public encryption keys for multiple users.
AI agents call getUsersPublicKeys to retrieve information from Xdevplatform/xmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing public encryption keys—a read-only operation. Public keys are intentionally shareable data, and retrieval does not modify state or trigger external operations. The action is informational only, consistent with the Read category.
From the tool's definition Tool name 'getUsersPublicKeys' and description 'Retrieve public encryption keys for multiple users' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Retrieve public encryption keys for multiple users. It is categorised as a Read tool in the Xdevplatform/xmcp MCP Server, which means it retrieves data without modifying state.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for getUsersPublicKeys: 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 Xdevplatform/xmcp. Nothing to install.
getUsersPublicKeys 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 getUsersPublicKeys 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 getUsersPublicKeys. 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.
getUsersPublicKeys is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
getUsersPublicKeys is one line of Xdevplatform/x's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →