// MCP TOOL REFERENCE

CLAUDER - RSTUDIO MCP SERVER TOOLS

13 tools from the ClaudeR - RStudio MCP Server MCP Server, categorised by risk level.

View the ClaudeR - RStudio MCP Server policy →

READ TOOLS

get_active_document Get the active document in RStudio 2/5 get_async_result Poll for async job results 2/5 get_r_info Get R environment information 2/5 get_session_history View execution history by agent 2/5 list_sessions List available RStudio sessions 2/5 read_file Read any text file from disk 3/5

WRITE TOOLS

connect_session Connect to a specific RStudio session 3/5 create_task_list Create a task list for analysis 2/5 modify_code_section Edit code in the active RStudio document 4/5 update_task_status Update task progress 2/5

EXECUTE TOOLS

execute_r Execute R code and return output 5/5 execute_r_async Run long-running R code in background 5/5 execute_r_with_plot Execute R code that generates a plot 5/5

// FAQ

How many tools does the ClaudeR - RStudio MCP Server MCP server have? +

The ClaudeR - RStudio MCP Server MCP server exposes 13 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on ClaudeR - RStudio MCP Server tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the ClaudeR - RStudio MCP Server server.

What risk categories do ClaudeR - RStudio MCP Server tools fall into? +

ClaudeR - RStudio MCP Server tools are categorised as Read (6), Write (4), Execute (3). Each category has a recommended default policy.

Enforce policies on ClaudeR - RStudio MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →