Low Risk

malware_get_cross_server_routes

Get Lenny Zeltser's Malware cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of malware_load_context. This server never requests your sample, analysis notes, or indicators and instruct...

Part of the Website Search server.

malware_get_cross_server_routes is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE WEBSITE SEARCH →

Free to start. No card required.

AI agents call malware_get_cross_server_routes to retrieve information from Website Search without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though malware_get_cross_server_routes only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "malware_get_cross_server_routes": {}
  }
}

See the full Website Search policy for all 53 tools.

Get this rule live on your own Website Search server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WEBSITE SEARCH →

View all 53 tools →

These attack patterns abuse exactly the kind of access malware_get_cross_server_routes gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so malware_get_cross_server_routes only ever does what you allow.

SECURE WEBSITE SEARCH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the malware_get_cross_server_routes tool do? +

Get Lenny Zeltser's Malware cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of malware_load_context. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.. It is categorised as a Read tool in the Website Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on malware_get_cross_server_routes? +

Register the Website Search MCP server in PolicyLayer and add a rule for malware_get_cross_server_routes: 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 Website Search. Nothing to install.

What risk level is malware_get_cross_server_routes? +

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

Can I rate-limit malware_get_cross_server_routes? +

Yes. Add a rate_limit block to the malware_get_cross_server_routes 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 malware_get_cross_server_routes completely? +

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

malware_get_cross_server_routes is provided by the Website Search MCP server (https://website-mcp.zeltser.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Website Search tool call.

Deterministic rules across all 53 Website Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.