get_session_history

// WHEN AI AGENTS USE THIS TOOL

AI agents call get_session_history to retrieve information from ClaudeR - RStudio MCP Server 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.

// WHY ENFORCE A POLICY ON GET_SESSION_HISTORY

Even though get_session_history 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.

// RECOMMENDED POLICY

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

clauder-rstudio-mcp-server.yaml

tools:
  get_session_history:
    rules:
      - action: allow

See the full ClaudeR - RStudio MCP Server policy for all 13 tools.

// DETAILS

Tool Name get_session_history

Category Read

MCP Server ClaudeR - RStudio MCP Server MCP Server

Risk Level Low

// MORE CLAUDER - RSTUDIO MCP SERVER TOOLS

Execute execute_r Execute execute_r_async Execute execute_r_with_plot Write connect_session Write create_task_list Write modify_code_section Write update_task_status Read get_active_document

View all 13 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

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

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the get_session_history tool do? +

View execution history by agent. It is categorised as a Read tool in the ClaudeR - RStudio MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_history? +

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

What risk level is get_session_history? +

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

Can I rate-limit get_session_history? +

Yes. Add a rate_limit block to the get_session_history 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 get_session_history completely? +

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

get_session_history is provided by the ClaudeR - RStudio MCP Server MCP server (clauder-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ClaudeR - RStudio MCP Server