Proxy get_engagement_status to the engagement-manager leaf MCP
AI agents call get_engagement_status 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 engagement status information without modifying any data. It acts as a proxy to fetch status from an external engagement-manager service. The read-only nature, lack of mutating operations, and context within a leave management system (where other tools show destructive operations like 'approve_leave' and 'apply_leave' which modify state) all point to a simple data retrieval function.
From the tool's definition Tool name 'get_engagement_status' and description 'Proxy get_engagement_status to the engagement-manager' indicate a query/retrieval operation. The verb 'get' and 'status' retrieval purpose confirm read-only behavior with no side effects.
Attacks that exploit this kind of access
Proxy get_engagement_status 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 get_engagement_status: 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.
get_engagement_status 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 get_engagement_status 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 get_engagement_status. 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.
get_engagement_status 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 →