List all your webhook bins with their URLs and stats
AI agents call list_bins to retrieve information from RequestBin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing webhook bins. It has no side effects, does not execute code, and does not modify or delete data. The blast radius of misuse is minimal — an attacker gains visibility into the user's bins but cannot create, modify, or destroy them. Classified as Read with low severity.
From the tool's definition Tool name is 'list_bins' and description states 'List all your webhook bins' — a pure retrieval operation that returns metadata (URLs and stats) without modifying or executing any resources.
Attacks that exploit this kind of access
List all your webhook bins with their URLs and stats. It is categorised as a Read tool in the RequestBin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RequestBin MCP Server MCP server in PolicyLayer and add a rule for list_bins: 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 RequestBin MCP Server. Nothing to install.
list_bins is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_bins 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.
Set action: deny in the PolicyLayer policy for list_bins. 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.
list_bins is provided by the RequestBin MCP Server MCP server (requestbin/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →