Check project against a compliance framework.
AI agents call check_compliance to retrieve information from Security-Use MCP Server 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 the state of a project against compliance standards, returning assessment results without modifying the project, deleting data, or executing code/commands. It is purely informational and has no blast radius beyond exposing compliance status, which could already be known to legitimate users. It belongs in the Read category with low severity.
From the tool's definition The tool 'check_compliance' performs a compliance check against a framework, which is a scanning and assessment operation with no side effects.
Attacks that exploit this kind of access
Check project against a compliance framework. It is categorised as a Read tool in the Security-Use MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Security-Use MCP Server MCP server in PolicyLayer and add a rule for check_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 Security-Use MCP Server. Nothing to install.
check_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 check_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 check_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.
check_compliance is provided by the Security-Use MCP Server MCP server (security-use/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 →