update_usage · Cursor Pro Limits MCP Server MCP

WHAT IT DOES

What update_usage does on Cursor Pro Limits MCP Server

AI agents use update_usage to create or update resources in Cursor Pro Limits MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cursor Pro Limits MCP Server environment.

WHY IT NEEDS A POLICY

Why update_usage needs a policy

This tool modifies usage statistics, which is a Write operation (reversible data modification). Severity is medium because while the tool itself doesn't delete data or execute arbitrary code, manipulating usage statistics could enable quota evasion, mask actual consumption patterns, or create billing discrepancies.

From the tool's definition Tool name 'update_usage' and description 'Update usage statistics (for testing or manual updates)' indicate data modification capability. The phrase 'manual updates' confirms this tool creates or modifies usage data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_usage Rate-limited

update_usage stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_usage": {
      "limits": [
        {
          "counter": "update_usage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cursor Pro Limits MCP Server, so you can run agents against it safely.

FAQ

Questions about update_usage

What does the update_usage tool do? +

Update usage statistics (for testing or manual updates). It is categorised as a Write tool in the Cursor Pro Limits MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_usage? +

Register the Cursor Pro Limits MCP Server MCP server in PolicyLayer and add a rule for update_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 update_usage? +

update_usage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_usage? +

Yes. Add a rate_limit block to the update_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 update_usage completely? +

Set action: deny in the PolicyLayer policy for update_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 update_usage? +

update_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.