Return effective OpenOCD/GDB runtime configuration with value sources.
AI agents call get_runtime_config 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 reads and returns runtime configuration information. It has no side effects—it does not execute commands, modify configuration, delete data, or trigger hardware operations. While it operates in a debugging context where configuration could be sensitive, the act itself is purely informational/read-only.
From the tool's definition Tool name 'get_runtime_config' and description 'Return effective OpenOCD/GDB runtime configuration with value sources' indicate a retrieval operation that queries and returns configuration state without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access get_runtime_config 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 get_runtime_config:
{
"version": "1",
"default": "deny",
"tools": {
"get_runtime_config": {}
}
}get_runtime_config 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.
Return effective OpenOCD/GDB runtime configuration with value sources. 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 get_runtime_config: 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.
get_runtime_config 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_runtime_config 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_runtime_config. 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_runtime_config 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.