openRouter_get_activity
Get usage metrics per model and day
This record as markdown: /tools/io-github-alifanov-scopegate/openrouter-get-activity.md
What openRouter_get_activity does on ScopeGate
AI agents call openRouter_get_activity 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.
Why openRouter_get_activity is rated Low
This tool fetches read-only usage/activity metrics. It queries existing data without modifying, creating, or deleting anything. Low severity as it only exposes usage statistics.
From the tool's definition "Get usage metrics per model and day" — retrieves informational data with no side effects
Attacks that exploit this kind of access
The rule that runs openRouter_get_activity 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_activity, this is the rule to start with:
openRouter_get_activity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every openRouter_get_activity call is checked against it from then on.
Questions about openRouter_get_activity
Get usage metrics per model and day. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for openRouter_get_activity: 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.
openRouter_get_activity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the openRouter_get_activity 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.
Set action: deny in the PolicyLayer policy for openRouter_get_activity. 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.
openRouter_get_activity 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.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue