Inspect an existing GraphQL integration, including endpoint, static headers/query params, and auth templates. Use this before repairing an integration with
AI agents call getIntegration to retrieve information from Executor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing integration configuration details (endpoint, headers, query parameters, auth templates). It has no side effects and does not modify, create, delete, or execute operations. It is a straightforward inspection/query operation with minimal security risk.
From the tool's definition Tool name 'getIntegration' and description 'Inspect an existing GraphQL integration' indicates retrieval of configuration data without modification. The verb 'inspect' and lack of any modification language confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access getIntegration gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Executor, and nothing reaches the server without passing your rules. This is the rule we recommend for getIntegration:
{
"version": "1",
"default": "deny",
"tools": {
"getIntegration": {}
}
}getIntegration is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inspect an existing GraphQL integration, including endpoint, static headers/query params, and auth templates. Use this before repairing an integration with. It is categorised as a Read tool in the Executor MCP Server, which means it retrieves data without modifying state.
Register the Executor MCP server in PolicyLayer and add a rule for getIntegration: 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 Executor. Nothing to install.
getIntegration 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 getIntegration 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 getIntegration. 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.
getIntegration is provided by the Executor MCP server (rhyssullivan/executor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Executor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Executor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.