Check an agent's compliance with regulatory frameworks. Supported frameworks: - SOC2: Service Organization Control 2 Type II - GDPR: EU General Data Protection Regulation - HIPAA: Health Insurance Portability and Accountability Act - PCI_DSS: Payment Card Industry Data Security Standard - CCPA: ...
Part of the Agentos MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call check_compliance to retrieve information from Agentos without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though check_compliance only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
check_compliance:
rules:
- action: allowSee the full Agentos policy for all 10 tools.
Agents calling read-class tools like check_compliance have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Check an agent's compliance with regulatory frameworks. Supported frameworks: - SOC2: Service Organization Control 2 Type II - GDPR: EU General Data Protection Regulation - HIPAA: Health Insurance Portability and Accountability Act - PCI_DSS: Payment Card Industry Data Security Standard - CCPA: California Consumer Privacy Act - NIST: NIST Cybersecurity Framework - ISO27001: ISO/IEC 27001 Information Security - FEDRAMP: Federal Risk and Authorization Management Program The compliance check evaluates: - Policy coverage for framework requirements - Audit trail completeness - Access control implementation - Data protection measures. It is categorised as a Read tool in the Agentos MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for check_compliance. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agentos MCP server.
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 Intercept 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 Intercept 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 Agentos MCP server (@microsoft/agentos-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.