List requests awaiting the manager's approval (scenario 8).
AI agents call list_pending_approvals to retrieve information from Attendance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of pending approval requests for display to a manager. It performs pure data retrieval with no ability to create, modify, delete, execute commands, or affect financial state. The only risk is potential information disclosure if an unauthorized user gains access, but that is a general authentication concern rather than a tool-specific capability risk.
From the tool's definition Tool name 'list_pending_approvals' and description 'List requests awaiting the manager's approval' indicate a retrieval operation with no modification or execution of side effects.
Attacks that exploit this kind of access
List requests awaiting the manager's approval (scenario 8). It is categorised as a Read tool in the Attendance MCP Server, which means it retrieves data without modifying state.
Register the Attendance MCP server in PolicyLayer and add a rule for list_pending_approvals: 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 Attendance. Nothing to install.
list_pending_approvals 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_pending_approvals 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_pending_approvals. 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_pending_approvals is provided by the Attendance MCP server (wenmaubipo/attendance-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 →