usage_limit_seconds

// WHEN AI AGENTS USE THIS TOOL

AI agents call usage_limit_seconds to retrieve information from Qiskit IBM Runtime MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON USAGE_LIMIT_SECONDS

Even though usage_limit_seconds only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

qiskit-ibm-runtime-mcp-server.yaml

tools:
  usage_limit_seconds:
    rules:
      - action: allow

See the full Qiskit IBM Runtime MCP Server policy for all 62 tools.

// DETAILS

Tool Name usage_limit_seconds

Category Read

MCP Server Qiskit IBM Runtime MCP Server MCP Server

Risk Level Low

// MORE QISKIT IBM RUNTIME MCP SERVER TOOLS

Destructive account_name Read account_info Read accounts Read adjacency_list Read average_path_length Read backend Read backend_name Read bidirectional

View all 62 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like usage_limit_seconds have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the usage_limit_seconds tool do? +

Total quota for the period. It is categorised as a Read tool in the Qiskit IBM Runtime MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on usage_limit_seconds? +

Add a rule in your Intercept YAML policy under the tools section for usage_limit_seconds. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Qiskit IBM Runtime MCP Server MCP server.

What risk level is usage_limit_seconds? +

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

Can I rate-limit usage_limit_seconds? +

Yes. Add a rate_limit block to the usage_limit_seconds rule in your Intercept 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 usage_limit_seconds completely? +

Set action: deny in the Intercept policy for usage_limit_seconds. 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 usage_limit_seconds? +

usage_limit_seconds is provided by the Qiskit IBM Runtime MCP Server MCP server (qiskit-ibm-runtime-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Qiskit IBM Runtime MCP Server