Check the status of an approval request
AI agents call beeboo_approval_check to retrieve information from BeeBoo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or checks the status of an existing approval request. It does not create, modify, delete, or execute any operations. It is a read-only query operation that has no impact on system state or data persistence. The blast radius of misuse is minimal—an agent could at worst view approval statuses it shouldn't see, which is a low-severity information disclosure risk rather than operational damage.
From the tool's definition Tool name is 'beeboo_approval_check' and description states 'Check the status of an approval request' — this is a pure query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Check the status of an approval request. It is categorised as a Read tool in the BeeBoo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BeeBoo MCP Server MCP server in PolicyLayer and add a rule for beeboo_approval_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 BeeBoo MCP Server. Nothing to install.
beeboo_approval_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 beeboo_approval_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 beeboo_approval_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.
beeboo_approval_check is provided by the BeeBoo MCP Server MCP server (tgm-ventures/beeboo-mcp). 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 →