AI agents call get_sla_compliance to retrieve information from Ppdm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries SLA compliance status—a read-only operation that returns information about backup schedules and compliance state. While it does not execute or modify anything, the sensitivity is elevated to 'medium' because the retrieved data (which assets are non-compliant) could inform decisions to bypass or disable security controls, or could be used to identify poorly-protected systems.
From the tool's definition Tool name is 'get_sla_compliance' and description states it 'Report[s] SLA compliance — which assets have not been backed up within the required window.' The verb 'report' and 'get' indicate data retrieval with no modification or execution of backup…
Attacks that exploit this kind of access
Report SLA compliance — which assets have not been backed up within the required window. It is categorised as a Read tool in the Ppdm MCP Server, which means it retrieves data without modifying state.
Register the Ppdm MCP server in PolicyLayer and add a rule for get_sla_compliance: 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 Ppdm. Nothing to install.
get_sla_compliance 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_sla_compliance 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_sla_compliance. 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_sla_compliance is provided by the Ppdm MCP server (moodswing9/ppdm-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 →