Get account usage limits.
AI agents call get_usage_limits to retrieve information from CustomGPT 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 account usage information without creating, modifying, deleting, or executing any operations. It is a simple data retrieval operation that has no impact on system state or resources. The low severity reflects the minimal risk of misuse—an agent retrieving usage limits poses no destructive, financial, or operational threat.
From the tool's definition Tool name 'get_usage_limits' and description 'Get account usage limits' indicate retrieval of read-only account metadata. The verb 'Get' and the informational nature of 'usage limits' (a query operation) with no side effects align with the Read category.
Attacks that exploit this kind of access
Get account usage limits. It is categorised as a Read tool in the CustomGPT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CustomGPT MCP Server MCP server in PolicyLayer and add a rule for get_usage_limits: 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 CustomGPT MCP Server. Nothing to install.
get_usage_limits 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_usage_limits 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_usage_limits. 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_usage_limits is provided by the CustomGPT MCP Server MCP server (poll-the-people/customgpt-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 →