Low Risk

query_credit_usage

Query detailed credit usage broken down by model and day. Supports date ranges up to 90 days.

How to control query_credit_usage ↓

What query_credit_usage does on Apple Shortcuts

AI agents call query_credit_usage to retrieve information from Apple Shortcuts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why query_credit_usage needs a policy

This tool retrieves historical credit usage metrics across specified date ranges (up to 90 days). It has no side effects—it does not create, modify, delete, or execute operations. The ability to examine billing/usage data is a standard Read operation.

From the tool's definition Tool name 'query_credit_usage' and description 'Query detailed credit usage' explicitly indicates data retrieval with 'Query' and no modifications.

Documented attack patterns abuse exactly the kind of access query_credit_usage gives an agent:

How to control query_credit_usage

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for query_credit_usage:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_credit_usage": {}
  }
}

query_credit_usage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Apple Shortcuts — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_credit_usage

What does the query_credit_usage tool do? +

Query detailed credit usage broken down by model and day. Supports date ranges up to 90 days. It is categorised as a Read tool in the Apple Shortcuts MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_credit_usage? +

Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for query_credit_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 Apple Shortcuts. Nothing to install.

What risk level is query_credit_usage? +

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

Can I rate-limit query_credit_usage? +

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

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

query_credit_usage is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apple Shortcuts tool call.

Start from Apple Shortcuts, 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.

423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.