cross_domain_evidence_stats

Get node and edge statistics for the shared cross-domain evidence graph.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/cross-domain-evidence-stats.md

WHAT IT DOES

What cross_domain_evidence_stats does on Jshookmcp

AI agents call cross_domain_evidence_stats to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why cross_domain_evidence_stats is rated Low

Tool retrieves statistics from an evidence graph; no data modification or external side effects.

From the tool's definition Get node and edge statistics for the shared cross-domain evidence graph.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cross_domain_evidence_stats 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_evidence_stats, this is the rule to start with:

cross_domain_evidence_stats Allowed

cross_domain_evidence_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cross_domain_evidence_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every cross_domain_evidence_stats call is checked against it from then on.

FAQ

Questions about cross_domain_evidence_stats

What does the cross_domain_evidence_stats tool do? +

Get node and edge statistics for the shared cross-domain evidence graph. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cross_domain_evidence_stats? +

Register the Jshook MCP server in PolicyLayer and add a rule for cross_domain_evidence_stats: 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.

What risk level is cross_domain_evidence_stats? +

cross_domain_evidence_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cross_domain_evidence_stats? +

Yes. Add a rate_limit block to the cross_domain_evidence_stats 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.

How do I block cross_domain_evidence_stats completely? +

Set action: deny in the PolicyLayer policy for cross_domain_evidence_stats. 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.

What MCP server provides cross_domain_evidence_stats? +

cross_domain_evidence_stats 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.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

cache_stats on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →