Ask questions about SubQuery Network Indexer; the agent will inspect the schema, validate and execute GraphQL queries, then summarize the results. Capabilities: • Project and deployment management • Indexer operations and stake tracking • Delegator relationships and rewards • Service agreements ...
Part of the SubQuery Network MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke graphql_agent to trigger processes or run actions in SubQuery Network. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
graphql_agent can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
graphql_agent:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full SubQuery Network policy for all 1 tools.
Agents calling execute-class tools like graphql_agent have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
graphql_agent is one of the high-risk operations in SubQuery Network. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Ask questions about SubQuery Network Indexer; the agent will inspect the schema, validate and execute GraphQL queries, then summarize the results. Capabilities: • Project and deployment management • Indexer operations and stake tracking • Delegator relationships and rewards • Service agreements and state channels • Era-based reward distribution • Token economics and SQT transfers • Airdrop campaigns and claims • Network governance and voting • Consumer query spending and refunds • Performance metrics and APY calculations • Dispute resolution and slashing • Allocation overflow tracking • Indexer labor history. It is categorised as a Execute tool in the SubQuery Network MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for graphql_agent. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SubQuery Network MCP server.
graphql_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the graphql_agent 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.
Set action: deny in the Intercept policy for graphql_agent. 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.
graphql_agent is provided by the SubQuery Network MCP server (SubQuery-Network/subquery-network). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept