Proxy list_active_engagements to the engagement-manager leaf MCP
AI agents call list_active_engagements to retrieve information from MCP Leave Management without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries engagement data without side effects. The 'list' verb combined with the proxy behavior to an engagement-manager service indicates a read-only operation that retrieves active engagements. No creation, modification, deletion, or execution of external commands is implied.
From the tool's definition Tool name 'list_active_engagements' with 'list' indicating retrieval operation. Description states 'Proxy list_active_engagements to the engagement-manager' confirming a data query/retrieval function with no modification or deletion capability.
Attacks that exploit this kind of access
Proxy list_active_engagements to the engagement-manager leaf MCP. It is categorised as a Read tool in the MCP Leave Management MCP Server, which means it retrieves data without modifying state.
Register the MCP Leave Management MCP server in PolicyLayer and add a rule for list_active_engagements: 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 MCP Leave Management. Nothing to install.
list_active_engagements 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_active_engagements 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_active_engagements. 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_active_engagements is provided by the MCP Leave Management MCP server (jaylathiatr/mcp-leave-management). 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 →