Low Risk

get_stored_response

Retrieve a stored HTTP response by its ID

How to control get_stored_response ↓

AI agents call get_stored_response 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

This tool only retrieves cached/stored HTTP responses by identifier. It performs a query operation with no capability to modify, delete, or execute external actions. The retrieval is scoped to already-stored responses, making it a straightforward read operation with minimal blast radius even if an agent misuses it.

From the tool's definition Tool name is 'get_stored_response' and description states 'Retrieve a stored HTTP response by its ID' — retrieves pre-existing data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_stored_response 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 get_stored_response:

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

get_stored_response 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 get_stored_response tool do? +

Retrieve a stored HTTP response by its ID. 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 get_stored_response? +

Register the MCP-RQuest MCP server in PolicyLayer and add a rule for get_stored_response: 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 get_stored_response? +

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

Can I rate-limit get_stored_response? +

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

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

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