Low Risk

http_options

Make an HTTP OPTIONS request to retrieve options for the specified URL

How to control http_options ↓

AI agents call http_options to retrieve information from MCP-RQuest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

HTTP OPTIONS is a metadata discovery method that retrieves allowed methods and capabilities for a resource. It has no side effects and does not modify any data, making it a Read operation with low severity.

From the tool's definition Make an HTTP OPTIONS request to retrieve options for the specified URL

Documented attack patterns abuse exactly the kind of access http_options gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-RQuest, and nothing reaches the server without passing your rules. This is the rule we recommend for http_options:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "http_options": {}
  }
}

http_options is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP-RQuest — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the http_options tool do? +

Make an HTTP OPTIONS request to retrieve options for the specified URL. It is categorised as a Read tool in the MCP-RQuest MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on http_options? +

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

What risk level is http_options? +

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

Can I rate-limit http_options? +

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

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

http_options is provided by the MCP-RQuest MCP server (xxxbrian/mcp-rquest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-RQuest tool call.

Deterministic rules across all 12 MCP-RQuest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 MCP-RQuest tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.