Run a raw GraphQL query against the sales API.
AI agents invoke graphql_query to trigger actions in MCP GraphQL Sales Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Executing raw/arbitrary GraphQL queries is an Execute-category action because the actual effects depend entirely on the query arguments. While the server is described as read-oriented (sales data), a raw GraphQL interface may expose mutations that can write or destructively modify data.
From the tool's definition "Run a raw GraphQL query against the sales API" — the tool executes arbitrary, user-supplied GraphQL queries.
Attacks that exploit this kind of access
Run a raw GraphQL query against the sales API. It is categorised as a Execute tool in the MCP GraphQL Sales Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP GraphQL Sales Server MCP server in PolicyLayer and add a rule for graphql_query: 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 MCP GraphQL Sales Server. Nothing to install.
graphql_query 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_query 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 graphql_query. 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_query is provided by the MCP GraphQL Sales Server MCP server (jambelg/mcp-graphql-claude). 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 →