get_ptp_logs

Get raw linuxptp daemon log entries from OpenShift cluster. Use dedicated tools (get_grandmaster_status, analyze_sync_status, get_clock_hierarchy) for structured analysis.

Server PTP MCP Server redhat-cne/ptp-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_ptp_logs does on PTP MCP Server

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

Why get_ptp_logs needs a policy

This tool queries and retrieves log entries from an OpenShift cluster's PTP daemon without creating, modifying, deleting, or executing operations. Log retrieval is a read-only operation with no side effects or destructive capability. The narrow scope (PTP daemon logs only) and lack of any write/execute/destructive capabilities result in low severity risk.

From the tool's definition Tool name 'get_ptp_logs' and description 'Get raw linuxptp daemon log entries' indicate retrieval of existing log data with no modification or side effects.

Questions about get_ptp_logs

What does the get_ptp_logs tool do? +

Get raw linuxptp daemon log entries from OpenShift cluster. Use dedicated tools (get_grandmaster_status, analyze_sync_status, get_clock_hierarchy) for structured analysis. It is categorised as a Read tool in the PTP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ptp_logs? +

Register the PTP MCP Server MCP server in PolicyLayer and add a rule for get_ptp_logs: 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.

What risk level is get_ptp_logs? +

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

Can I rate-limit get_ptp_logs? +

Yes. Add a rate_limit block to the get_ptp_logs 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_ptp_logs completely? +

Set action: deny in the PolicyLayer policy for get_ptp_logs. 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_ptp_logs? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.