fetch_response_headers

What fetch_response_headers does on Allcanuse

AI agents call fetch_response_headers 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.

Why fetch_response_headers is rated Low

Fetching response headers is a read-only network diagnostic operation that queries HTTP metadata without modifying data, executing code, or causing side effects. Consistent with the server's stated purpose of 'network diagnostics.' Low severity due to minimal blast radius—response headers are typically non-sensitive metadata, though confidence is reduced by the absent description.

From the tool's definition Tool name 'fetch_response_headers' indicates retrieval of HTTP response headers from network requests; the prefix 'fetch' denotes a read operation. Description is empty, limiting certainty slightly.

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

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

Questions about fetch_response_headers