New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

export_session_script

Write session operations as a Python replay script.

SERVERDocx SOURCEsecurityronin/docx-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/export-session-script.md

What export_session_script does on Docx

AI agents use export_session_script to create or update resources in Docx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.

Why export_session_script is rated Medium

This tool creates or generates a new Python script file based on session operations, which is reversible (the file can be deleted or overwritten). It does not execute code, delete irreversibly, or modify the document itself—it exports a representation of operations to a new artifact. This is a Write-category operation.

From the tool's definition Tool name 'export_session_script' combined with description 'Write session operations as a Python replay script' indicates generation and persistence of code artifacts. The verb 'Write' and action of creating a script file constitute data creation.

Questions about export_session_script

What does the export_session_script tool do? +

Write session operations as a Python replay script. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_session_script? +

Register the Docx MCP server in PolicyLayer and add a rule for export_session_script: 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 export_session_script? +

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

Can I rate-limit export_session_script? +

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

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

export_session_script 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.

More on Docx, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Docx's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.