Low Risk

renv_status

Report whether the project library is synchronised with renv.lock using renv::status().

Part of the R Packagedev MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call renv_status to retrieve information from R Packagedev without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though renv_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-b0ydt-r-packagedev-mcp.yaml
tools:
  renv_status:
    rules:
      - action: allow

See the full R Packagedev policy for all 30 tools.

Tool Name renv_status
Category Read
Risk Level Low

View all 30 tools →

Agents calling read-class tools like renv_status have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the renv_status tool do? +

Report whether the project library is synchronised with renv.lock using renv::status().. It is categorised as a Read tool in the R Packagedev MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on renv_status? +

Add a rule in your Intercept YAML policy under the tools section for renv_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the R Packagedev MCP server.

What risk level is renv_status? +

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

Can I rate-limit renv_status? +

Yes. Add a rate_limit block to the renv_status rule in your Intercept 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 renv_status completely? +

Set action: deny in the Intercept policy for renv_status. 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 renv_status? +

renv_status is provided by the R Packagedev MCP server (r-packagedev-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on R Packagedev

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.