get_service_usage

Get usage statistics for a specific service

Server Cursor Pro Limits MCP Server mehmetfiskindal/cursor-pro-limits-mcp
Category Read
Risk class Low
Parameters 00 required

What get_service_usage does on Cursor Pro Limits MCP Server

AI agents call get_service_usage to retrieve information from Cursor Pro Limits MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_service_usage needs a policy

This tool retrieves or queries usage data without creating, modifying, or deleting information. It is a read-only operation that returns statistics. While the data may be sensitive (financial/subscription details), the tool itself performs no destructive or financial operations—it only fetches information. Severity is low because misuse would only expose data, not cause irreversible harm or financial loss.

From the tool's definition Tool name 'get_service_usage' and description 'Get usage statistics for a specific service' indicate a query/retrieval operation. The server description confirms this is for 'monitoring' and 'tracking' usage with no mention of modifications.

Questions about get_service_usage

What does the get_service_usage tool do? +

Get usage statistics for a specific service. It is categorised as a Read tool in the Cursor Pro Limits MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_service_usage? +

Register the Cursor Pro Limits MCP Server MCP server in PolicyLayer and add a rule for get_service_usage: 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 Pro Limits MCP Server. Nothing to install.

What risk level is get_service_usage? +

get_service_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_service_usage? +

Yes. Add a rate_limit block to the get_service_usage 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.

How do I block get_service_usage completely? +

Set action: deny in the PolicyLayer policy for get_service_usage. 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.

What MCP server provides get_service_usage? +

get_service_usage is provided by the Cursor Pro Limits MCP Server MCP server (mehmetfiskindal/cursor-pro-limits-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.