Check the health status of the Bruno MCP server and Bruno CLI
AI agents call bruno_health_check 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 a health/status check, which is a read-only diagnostic operation that retrieves information about system state without modifying, executing external commands, or affecting any data. It falls clearly into the Read category with low severity since health checks have no blast radius—they cannot be misused to cause harm regardless of how an AI agent invokes them.
From the tool's definition Tool name 'bruno_health_check' and description 'Check the health status of the Bruno MCP server and Bruno CLI' indicate a diagnostic query operation with no side effects.
Attacks that exploit this kind of access
Check the health status of the Bruno MCP server and Bruno CLI. 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_health_check: 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_health_check 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_health_check 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_health_check. 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_health_check 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 →