Get current PTP clock hierarchy and topology
AI agents call get_clock_hierarchy to retrieve information from PTP 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 and displays information about PTP clock hierarchy and network topology. It performs no modifications, deletions, or command execution—it only reads and presents data about the current system state. This is a classic Read category tool with low severity risk, as misuse would only expose timing/topology information without side effects.
From the tool's definition The tool name 'get_clock_hierarchy' and description 'Get current PTP clock hierarchy and topology' indicate a retrieval operation that queries the state of PTP clock systems without modifying or executing operations.
Attacks that exploit this kind of access
Get current PTP clock hierarchy and topology. It is categorised as a Read tool in the PTP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PTP MCP Server MCP server in PolicyLayer and add a rule for get_clock_hierarchy: 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 PTP MCP Server. Nothing to install.
get_clock_hierarchy 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_clock_hierarchy 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_clock_hierarchy. 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_clock_hierarchy is provided by the PTP MCP Server MCP server (redhat-cne/ptp-mcp-server). 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 →