Skip to main content
Glama

security-crypto

referrer_policy_audit

Evaluate HTTP Referrer-Policy values for cross-origin query string/URL leakage risk and recommend strict alternatives.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "referrer_policy_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
policyNostrict-origin-when-cross-origin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and 'evaluate' plus 'recommend' does signal a non-mutating analysis that returns advice rather than performing changes. However, it says nothing about what the evaluation returns, whether a risk verdict or severity is included, or how the two input modes differ behaviorally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence covering the target, the risk dimension, and the output. It is efficient with no filler, though the brevity leaves little room for the parameter clarification the schema lacks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description implies a useful return (a risk assessment plus stricter alternatives), which partly compensates for the missing output schema. But for a two-parameter tool with zero schema documentation and no annotations, it is not complete: the 'text' vs 'policy' input contract and the meaning of the default remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, and the description adds no meaning: it never explains what 'text' accepts versus what 'policy' accepts, whether one is a raw header string and the other a token, or what happens when only the defaulted 'policy' is supplied. This distinction is exactly what an agent needs and it is absent from both description and schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb ('Evaluate') and a specific resource ('HTTP Referrer-Policy values'), and further scopes the analysis to cross-origin query-string/URL leakage risk plus a recommendation output. That is enough to separate it from policy-adjacent siblings like permissions_policy_audit or csp_parse_and_audit, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for checking a Referrer-Policy setting for leakage risk, but the description never states when to reach for this instead of a related audit tool, nor any prerequisites or exclusions. No misleading guidance, just no explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources