get_eox_devices
AI agents call get_eox_devices 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 is a read-only data retrieval tool that queries Cisco Catalyst Center for end-of-life device information. It returns status/advisory data with no side effects. Confidence is not higher due to empty tool description, but the naming convention and context strongly indicate passive data retrieval.
From the tool's definition Tool name 'get_eox_devices' follows the 'get_*' retrieval pattern consistent with sibling tools (get_client_counts, get_compliance_detail, get_eox_summary, etc.).
Attacks that exploit this kind of access
get_eox_devices. 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_eox_devices: 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_eox_devices 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_eox_devices 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_eox_devices. 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_eox_devices 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 →