get_eox_device_details

get_eox_device_details

Server Cisco Catalyst Center MCP Server martynrees/catalyst-mcp
Category Read
Risk class Low
Parameters 00 required

What get_eox_device_details does on Cisco Catalyst Center MCP Server

AI agents call get_eox_device_details 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.

Why get_eox_device_details needs a policy

This tool retrieves details about end-of-life (EoX) devices for monitoring and compliance purposes. Retrieval operations have no side effects and fit the Read category. Confidence is moderately high based on naming conventions and server context, but slightly reduced due to empty description. Severity is low because read access to device lifecycle information poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_eox_device_details' indicates a GET/retrieval operation. No description provided, but context from sibling tools (get_eox_devices, get_eox_summary, get_compliance_detail, etc.) confirms this server's pattern of read-only monitoring and data…

Questions about get_eox_device_details

What does the get_eox_device_details tool do? +

get_eox_device_details. It is categorised as a Read tool in the Cisco Catalyst Center MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_eox_device_details? +

Register the Cisco Catalyst Center MCP Server MCP server in PolicyLayer and add a rule for get_eox_device_details: 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.

What risk level is get_eox_device_details? +

get_eox_device_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_eox_device_details? +

Yes. Add a rate_limit block to the get_eox_device_details 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.

How do I block get_eox_device_details completely? +

Set action: deny in the PolicyLayer policy for get_eox_device_details. 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.

What MCP server provides get_eox_device_details? +

get_eox_device_details 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.

// THE FULL RECORD

get_eox_device_details is one line of Cisco Catalyst Center MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.