Get full details for a specific register within a peripheral, including address offset, size, access type, reset value, and all bit-fields with their positions. Use this when you need exact register layout for low-level firmware code.
AI agents call lookup_register to retrieve information from Mcp Svd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—it queries an SVD database to obtain register specifications and metadata. The description contains no language indicating write, modification, execution, or deletion capabilities. The function is to provide read-only access to ARM CMSIS hardware definitions for reference during firmware development.
From the tool's definition Tool retrieves 'full details for a specific register' including 'address offset, size, access type, reset value, and all bit-fields'. The verb is 'Get' and the description emphasizes querying hardware register definitions without modification capabilities.
Attacks that exploit this kind of access
Get full details for a specific register within a peripheral, including address offset, size, access type, reset value, and all bit-fields with their positions. Use this when you need exact register layout for low-level firmware code. It is categorised as a Read tool in the Mcp Svd MCP Server, which means it retrieves data without modifying state.
Register the Mcp Svd MCP server in PolicyLayer and add a rule for lookup_register: 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 Mcp Svd. Nothing to install.
lookup_register 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 lookup_register 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 lookup_register. 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.
lookup_register is provided by the Mcp Svd MCP server (pkt-lab/mcp-svd). 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 →