Execute GraphQL queries against LSMS or LERG. These are DISTINCT APIs with different schemas — do not mix their syntax. LSMS (service=
AI agents invoke graphql_query to trigger actions in Telique MCP. 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.
The tool runs arbitrary GraphQL queries supplied by the caller against two distinct backend APIs (LSMS and LERG). While GraphQL is often read-oriented, arbitrary query execution can include mutations, and the open-ended nature of the tool means an AI agent could construct queries with unintended scope or side effects.
From the tool's definition "Execute GraphQL queries against LSMS or LERG" — the tool explicitly executes arbitrary GraphQL queries against backend APIs
Attacks that exploit this kind of access
Execute GraphQL queries against LSMS or LERG. These are DISTINCT APIs with different schemas — do not mix their syntax. LSMS (service=. It is categorised as a Execute tool in the Telique MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Telique 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 Telique MCP. 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 Telique MCP server (ringer/telique-mcp). 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 →