Low Risk

get_latest_request

Get the most recent request sent to a webhook.site endpoint.

How to control get_latest_request ↓

What get_latest_request does on Webhook Site MCP Server

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

Low Risk

Why get_latest_request needs a policy

This tool performs data retrieval only. It queries and returns information about an incoming request without modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only read captured request data they have access to.

From the tool's definition The tool 'get_latest_request' retrieves 'the most recent request sent to a webhook.site endpoint' — a query operation with no side effects.

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

How to control get_latest_request

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

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

get_latest_request 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 Webhook Site MCP Server — 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.

Related tools and policies

Go deeper

Questions about get_latest_request

What does the get_latest_request tool do? +

Get the most recent request sent to a webhook.site endpoint. It is categorised as a Read tool in the Webhook Site MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_latest_request? +

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

What risk level is get_latest_request? +

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

Can I rate-limit get_latest_request? +

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

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

get_latest_request is provided by the Webhook Site MCP Server MCP server (zebbern/webhook-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Webhook Site MCP Server tool call.

Start from Webhook Site MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

23 Webhook Site MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.