set_x_hospital · OpenAPI REST MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_x_hospital does on OpenAPI REST MCP Server

AI agents use set_x_hospital 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 set_x_hospital needs a policy

This tool modifies request headers used for downstream API calls. While header configuration is technically a write operation affecting request metadata (not data), the severity is medium rather than high because: (1) it only modifies headers, not core data or system state; (2) the effect is scoped to a single header; (3) changes are reversible via clear_header_context or setting a new value.

From the tool's definition Tool description states it 'Set[s] the x-hospital header value' for 'downstream API requests', indicating modification of request configuration state that affects subsequent operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_x_hospital Rate-limited

set_x_hospital 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": {
    "set_x_hospital": {
      "limits": [
        {
          "counter": "set_x_hospital_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 set_x_hospital

What does the set_x_hospital tool do? +

Set the x-hospital header value to use for downstream API requests (overrides environment default). 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 set_x_hospital? +

Register the OpenAPI REST MCP Server MCP server in PolicyLayer and add a rule for set_x_hospital: 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 set_x_hospital? +

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

Can I rate-limit set_x_hospital? +

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

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

set_x_hospital 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.