get_session_log

Return all operations performed this session as replayable JSON.

SERVERDocx SOURCEsecurityronin/docx-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/get-session-log.md

WHAT IT DOES

What get_session_log does on Docx

AI agents call get_session_log to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_session_log is rated Low

This tool retrieves historical session information in a structured format. It performs a read-only query operation that does not modify, create, execute, delete, or transfer data. The 'replayable JSON' output is informational only. No external operations are triggered, no code is executed, and no document state is changed. This is purely a data retrieval function.

From the tool's definition Tool name 'get_session_log' and description 'Return all operations performed this session as replayable JSON' indicate retrieval and querying of session data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_session_log safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_session_log, this is the rule to start with:

get_session_log Allowed

get_session_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_session_log": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every get_session_log call is checked against it from then on.

FAQ

Questions about get_session_log

What does the get_session_log tool do? +

Return all operations performed this session as replayable JSON. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_log? +

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

What risk level is get_session_log? +

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

Can I rate-limit get_session_log? +

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

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

get_session_log is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →