trace_http_redirects

A read tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

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/ra1nyxin-allcanuse-mcp/trace-http-redirects.md

WHAT IT DOES

What trace_http_redirects does on Allcanuse

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

RISK

Why trace_http_redirects is rated Low

The name implies a diagnostic/read operation that follows HTTP redirects to trace their chain, similar to network diagnostics. No description to confirm, but given the server context of 'network diagnostics' among its capabilities and the tool name, this is most likely a read/query operation with no side effects. Confidence is reduced due to empty description.

From the tool's definition Tool name 'trace_http_redirects' suggests following/reading HTTP redirect chains; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trace_http_redirects safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trace_http_redirects, this is the rule to start with:

trace_http_redirects Allowed

trace_http_redirects 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": {
    "trace_http_redirects": {}
  }
}

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

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

FAQ

Questions about trace_http_redirects

What does the trace_http_redirects tool do? +

trace_http_redirects is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on trace_http_redirects? +

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

What risk level is trace_http_redirects? +

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

Can I rate-limit trace_http_redirects? +

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

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

trace_http_redirects is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

The MCP Attack Database →

Guides

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