openRouter_get_key_info

Get API key details including daily, weekly, and monthly spend

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/openrouter-get-key-info.md

WHAT IT DOES

What openRouter_get_key_info does on ScopeGate

AI agents call openRouter_get_key_info to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why openRouter_get_key_info is rated Low

This tool retrieves read-only information about an API key's usage and spending metrics. It does not modify data, execute commands, or move money — it only fetches/reports existing spend data. Severity is low since misuse only exposes spend/usage telemetry, not credentials or sensitive PII.

From the tool's definition 'Get API key details including daily, weekly, and monthly spend'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs openRouter_get_key_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openRouter_get_key_info, this is the rule to start with:

openRouter_get_key_info Allowed

openRouter_get_key_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openRouter_get_key_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every openRouter_get_key_info call is checked against it from then on.

FAQ

Questions about openRouter_get_key_info

What does the openRouter_get_key_info tool do? +

Get API key details including daily, weekly, and monthly spend. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openRouter_get_key_info? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for openRouter_get_key_info: 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 ScopeGate. Nothing to install.

What risk level is openRouter_get_key_info? +

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

Can I rate-limit openRouter_get_key_info? +

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

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

openRouter_get_key_info is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →