Retrieve information about the API key being used for authentication
AI agents call get_api_key_info to retrieve information from Cursor Cloud Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_api_key_info only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Retrieve information about the API key being used for authentication. It is categorised as a Read tool in the Cursor Cloud Agent MCP Server, which means it retrieves data without modifying state.
Register the Cursor Cloud Agent MCP server in PolicyLayer and add a rule for get_api_key_info: 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 Cursor Cloud Agent. Nothing to install.
get_api_key_info 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_api_key_info 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_api_key_info. 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_api_key_info is provided by the Cursor Cloud Agent MCP server (willpowell8/cursor-cloud-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.