All available GraphQL queries
AI agents call queries to retrieve information from GraphQL Schema Explorer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists information about available GraphQL queries without executing them or modifying data. It is a read-only introspection operation that helps users understand what queries exist in a GraphQL API. While the actual queries returned could theoretically be used to trigger data retrieval, the tool itself merely exposes the schema—it does not execute queries, create, modify, or delete data.
From the tool's definition Tool description states it lists 'All available GraphQL queries', which is introspection and discovery. Combined with sibling tools like 'search', 'schema', 'types', and 'field' that indicate schema exploration functionality.
Attacks that exploit this kind of access
All available GraphQL queries. It is categorised as a Read tool in the GraphQL Schema Explorer MCP Server, which means it retrieves data without modifying state.
Register the GraphQL Schema Explorer MCP server in PolicyLayer and add a rule for queries: 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 GraphQL Schema Explorer. Nothing to install.
queries 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 queries 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 queries. 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.
queries is provided by the GraphQL Schema Explorer MCP server (martinshumberto/mcp-server-graphql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →