Read RTT log from the active debug session. Returns up to max_lines of output.
AI agents call read_rtt to retrieve information from Openocd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Real-Time Transfer (RTT) logs from an active debug session. The operation is purely informational—it queries and returns existing debug output without creating, modifying, deleting, or executing any code. The max_lines parameter further confirms it is a bounded read operation. No side effects occur on the target system or data. This is a classic Read category tool.
From the tool's definition Tool name 'read_rtt' and description 'Read RTT log from the active debug session. Returns up to max_lines of output.' explicitly indicate a read-only operation that retrieves existing log data without modification or side effects.
Documented attack patterns abuse exactly the kind of access read_rtt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openocd, and nothing reaches the server without passing your rules. This is the rule we recommend for read_rtt:
{
"version": "1",
"default": "deny",
"tools": {
"read_rtt": {}
}
}read_rtt is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read RTT log from the active debug session. Returns up to max_lines of output. It is categorised as a Read tool in the Openocd MCP Server, which means it retrieves data without modifying state.
Register the Openocd MCP server in PolicyLayer and add a rule for read_rtt: 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 Openocd. Nothing to install.
read_rtt 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 read_rtt 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 read_rtt. 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.
read_rtt is provided by the Openocd MCP server (luiox/openocd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openocd, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Openocd tools catalogued and risk-classified — across an index of 43,000+ MCP servers.