clear_header_context · OpenAPI REST MCP Server MCP

WHAT IT DOES

What clear_header_context does on OpenAPI REST MCP Server

AI agents use clear_header_context to create or update resources in OpenAPI REST MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenAPI REST MCP Server environment.

WHY IT NEEDS A POLICY

Why clear_header_context needs a policy

This tool clears/resets header context overrides, reverting to default values. This is a modification of state (Write) rather than a destructive action since it reverts to defaults rather than permanently deleting data. The blast radius is low as it only affects header context configuration, not persistent data.

From the tool's definition Clear user-provided x-group and x-hospital overrides (revert to defaults)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clear_header_context Rate-limited

clear_header_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clear_header_context": {
      "limits": [
        {
          "counter": "clear_header_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OpenAPI REST MCP Server, so you can run agents against it safely.

FAQ

Questions about clear_header_context

What does the clear_header_context tool do? +

Clear user-provided x-group and x-hospital overrides (revert to defaults). It is categorised as a Write tool in the OpenAPI REST MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clear_header_context? +

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

What risk level is clear_header_context? +

clear_header_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clear_header_context? +

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

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

clear_header_context is provided by the OpenAPI REST MCP Server MCP server (saranazeer27/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.