Get API key information including name, creation date, and user email. Use this to verify authentication is working correctly. Usage Example: \
AI agents call get_me to retrieve information from Cloud Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves authentication and metadata information about the current API key without modifying, executing, or deleting anything. It is a diagnostic read operation used to verify the authenticated user's identity and session status. While it reveals some user information, the blast radius is minimal as it only returns data about the requesting user's own authentication context.
From the tool's definition Tool description states 'Get API key information including name, creation date, and user email' and 'verify authentication is working correctly'.
Documented attack patterns abuse exactly the kind of access get_me gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cloud Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_me:
{
"version": "1",
"default": "deny",
"tools": {
"get_me": {}
}
} get_me is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get API key information including name, creation date, and user email. Use this to verify authentication is working correctly. Usage Example: \. It is categorised as a Read tool in the Cloud Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cloud Agent MCP Server MCP server in PolicyLayer and add a rule for get_me: 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 Cloud Agent MCP Server. Nothing to install.
get_me 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 get_me 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 get_me. 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.
get_me is provided by the Cloud Agent MCP Server MCP server (jxnl/cursor-cloud-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cloud Agent MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Cloud Agent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.