Get detailed information about a specific request without executing it
AI agents call bruno_get_request_details to retrieve information from Bruno MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only (getting details about a request). The explicit statement that it does not execute the request confirms it is a Read operation with no side effects. The severity is low because it only accesses existing request metadata from the collection, with no impact on systems, data integrity, or external services.
From the tool's definition Tool description states 'Get detailed information about a specific request without executing it' - retrieves metadata about a request without side effects.
Attacks that exploit this kind of access
Get detailed information about a specific request without executing it. It is categorised as a Read tool in the Bruno MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bruno MCP Server MCP server in PolicyLayer and add a rule for bruno_get_request_details: 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 Bruno MCP Server. Nothing to install.
bruno_get_request_details 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 bruno_get_request_details 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 bruno_get_request_details. 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.
bruno_get_request_details is provided by the Bruno MCP Server MCP server (jcr82/bruno-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 →