correlate_sweep
Run a 40-tool broad sweep on the query and return the cross-tool entity graph: emails/domains/IPs/handles/phones appearing in >=2 tools, strongest first. This is the connected-pattern signal.
This record as markdown: /tools/com-thetempleofdoom-osint-mcp-osint-terminal/correlate-sweep.md
What correlate_sweep does on Osint Terminal
AI agents invoke correlate_sweep to trigger actions in Osint Terminal. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes |
Parameters from the server's own tool schema.
Why correlate_sweep is rated High
correlate_sweep triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs correlate_sweep safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Osint Terminal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For correlate_sweep, this is the rule to start with:
correlate_sweep stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Osint Terminal, apply this rule, and every correlate_sweep call is checked against it from then on.
Questions about correlate_sweep
Run a 40-tool broad sweep on the query and return the cross-tool entity graph: emails/domains/IPs/handles/phones appearing in >=2 tools, strongest first. This is the connected-pattern signal. It is categorised as a Execute tool in the Osint Terminal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
correlate_sweep accepts 1 parameter: q. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Osint Terminal MCP server in PolicyLayer and add a rule for correlate_sweep: 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 Osint Terminal. Nothing to install.
correlate_sweep 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 correlate_sweep 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 correlate_sweep. 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.
correlate_sweep is provided by the Osint Terminal MCP server (https://osint-mcp.thetempleofdoom.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Osint Terminal, and thousands of servers like it.
Across the catalogue