Medium Risk

renv_init

Initialise an renv project-local library for the project using renv::init(). Creates renv/ and renv.lock, and updates .Rprofile.

Part of the R Packagedev server.

renv_init can modify R Packagedev data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE R PACKAGEDEV →

Free to start. No card required.

AI agents use renv_init to create or modify resources in R Packagedev. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call renv_init repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach R Packagedev.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "renv_init": {
      "limits": [
        {
          "counter": "renv_init_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full R Packagedev policy for all 30 tools.

Get this rule live on your own R Packagedev server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY R PACKAGEDEV →

View all 30 tools →

These attack patterns abuse exactly the kind of access renv_init gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so renv_init only ever does what you allow.

SECURE R PACKAGEDEV →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the renv_init tool do? +

Initialise an renv project-local library for the project using renv::init(). Creates renv/ and renv.lock, and updates .Rprofile.. It is categorised as a Write tool in the R Packagedev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on renv_init? +

Register the R Packagedev MCP server in PolicyLayer and add a rule for renv_init: 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 R Packagedev. Nothing to install.

What risk level is renv_init? +

renv_init is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit renv_init? +

Yes. Add a rate_limit block to the renv_init 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.

How do I block renv_init completely? +

Set action: deny in the PolicyLayer policy for renv_init. 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_init? +

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

Enforce policy on every R Packagedev tool call.

Deterministic rules across all 30 R Packagedev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.