Validates project against compliance frameworks
AI agents call check_compliance to retrieve information from MCP Shamash without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs compliance validation—a read-only assessment against frameworks like OWASP, CIS, and NIST. It retrieves or analyzes project state against compliance rules without creating, modifying, executing code, deleting data, or committing financial actions. The blast radius of misuse is low since it only produces informational output about compliance status.
From the tool's definition Tool name 'check_compliance' with description 'Validates project against compliance frameworks' indicates a query/assessment operation. The verb 'validates' and 'check' are passive analysis operations with no modification or execution.
Attacks that exploit this kind of access
Validates project against compliance frameworks. It is categorised as a Read tool in the MCP Shamash MCP Server, which means it retrieves data without modifying state.
Register the MCP Shamash 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 MCP Shamash. 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 MCP Shamash MCP server (neotecdigital/mcp_shamash). 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 →