Look up PTP runtime config file paths from profile names. Returns a mapping of profile names to their config file paths inside the linuxptp daemon pod. Useful for discovering which profiles are active and resolving profile names to config file paths for use with run_pmc_query.
AI agents call get_ptp_runtime_configs 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 maps configuration metadata from a running PTP daemon pod. It performs a lookup operation that queries existing state without making any changes, executing commands, or triggering external operations.
From the tool's definition Tool description states it "Look[s] up PTP runtime config file paths" and "Returns a mapping" - purely retrieval/query operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Look up PTP runtime config file paths from profile names. Returns a mapping of profile names to their config file paths inside the linuxptp daemon pod. Useful for discovering which profiles are active and resolving profile names to config file paths for use with run_pmc_query. 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_ptp_runtime_configs: 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_ptp_runtime_configs 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_ptp_runtime_configs 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_ptp_runtime_configs. 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_ptp_runtime_configs 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 →