Given a URL, ask every plugin whether it recognizes it, returning best-confidence matches so the UI can pre-fill onboarding for the right plugin.
AI agents call integrations.detect 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.
The tool performs passive reconnaissance against a given URL by querying plugins for recognition capabilities. It retrieves and returns metadata about plugin recognition without modifying state, executing code, or causing side effects. This is a classic Read operation—data retrieval with no blast radius beyond information disclosure about which plugins recognize a URL.
From the tool's definition Tool description states it 'ask[s] every plugin whether it recognizes it' and returns 'matches' for UI pre-filling. This is a query/detection operation with no data modification, deletion, or command execution.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access integrations.detect 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 integrations.detect:
{
"version": "1",
"default": "deny",
"tools": {
"integrations.detect": {}
}
}integrations.detect 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.
Given a URL, ask every plugin whether it recognizes it, returning best-confidence matches so the UI can pre-fill onboarding for the right plugin. 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 integrations.detect: 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.
integrations.detect 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 integrations.detect 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 integrations.detect. 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.
integrations.detect 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.