cross_domain_correlate_all
Run the built-in skia, mojo, syscall, and binary correlators and merge the results into the shared evidence graph.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/cross-domain-correlate-all.md
What cross_domain_correlate_all does on Jshookmcp
AI agents invoke cross_domain_correlate_all to trigger actions in Jshookmcp. 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.
Why cross_domain_correlate_all is rated High
Executes multiple analysis engines with side effects on a shared evidence graph.
From the tool's definition Run built-in correlators, merge results into shared evidence graph.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cross_domain_correlate_all safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cross_domain_correlate_all, this is the rule to start with:
cross_domain_correlate_all 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 Jshookmcp, apply this rule, and every cross_domain_correlate_all call is checked against it from then on.
Questions about cross_domain_correlate_all
Run the built-in skia, mojo, syscall, and binary correlators and merge the results into the shared evidence graph. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jshook MCP server in PolicyLayer and add a rule for cross_domain_correlate_all: 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 Jshookmcp. Nothing to install.
cross_domain_correlate_all 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 cross_domain_correlate_all 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 cross_domain_correlate_all. 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.
cross_domain_correlate_all is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue