get_compliance_count
AI agents call get_compliance_count to retrieve information from Cisco Catalyst Center 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 compliance count metrics from Cisco Catalyst Center for monitoring purposes. As a counting/retrieval operation with no side effects, it falls under the Read category. The low severity reflects that misuse would only expose network compliance metrics without enabling changes or destructive actions.
From the tool's definition Tool name 'get_compliance_count' follows read-only pattern consistent with sibling tools (get_client_counts, get_compliance_detail, get_issues, etc.). The 'get_' prefix and 'count' operation indicate data retrieval with no modification.
Attacks that exploit this kind of access
get_compliance_count. It is categorised as a Read tool in the Cisco Catalyst Center MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cisco Catalyst Center MCP Server MCP server in PolicyLayer and add a rule for get_compliance_count: 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 Cisco Catalyst Center MCP Server. Nothing to install.
get_compliance_count 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_compliance_count 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_compliance_count. 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_compliance_count is provided by the Cisco Catalyst Center MCP Server MCP server (martynrees/catalyst-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 →