Read the contents of a file from the nRF Connect SDK repo (nrfconnect/sdk-nrf @ ${REF}). Works for any text file: .rst documentation, .c/.h source, CMakeLists.txt, Kconfig, prj.conf, .yaml, README.rst, etc. Supports optional startLine/endLine to read a specific range (1-indexed), useful for large...
AI agents call nrf_read to retrieve information from Nrf without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool exclusively retrieves and queries file contents from the nRF Connect SDK repository without any side effects. It does not create, modify, delete, or execute code—it only reads documentation and source files. This is a straightforward Read category tool with low severity risk.
From the tool's definition Tool description states it 'Read the contents of a file' and 'Works for any text file: .rst documentation, .c/.h source, CMakeLists.txt, Kconfig, prj.conf, .yaml, README.rst, etc.' It supports optional startLine/endLine parameters to read specific ranges.
Attacks that exploit this kind of access
Read the contents of a file from the nRF Connect SDK repo (nrfconnect/sdk-nrf @ ${REF}). Works for any text file: .rst documentation, .c/.h source, CMakeLists.txt, Kconfig, prj.conf, .yaml, README.rst, etc. Supports optional startLine/endLine to read a specific range (1-indexed), useful for large files. For files over 500 KB, the first 2000 lines are returned automatically with a truncation notice. Use nrf_list to discover paths first. Examples: -. It is categorised as a Read tool in the Nrf MCP Server, which means it retrieves data without modifying state.
Register the Nrf MCP server in PolicyLayer and add a rule for nrf_read: 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 Nrf. Nothing to install.
nrf_read 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 nrf_read 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 nrf_read. 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.
nrf_read is provided by the Nrf MCP server (pshanesmith/nrf-mcp). 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 →