thompson_write
Transform complex content into Thompson Protocol format — plain English mandate, intuition-before-mechanics, analogy-per-concept. Returns structured sections with jargon translations and readability scores.
This record as markdown: /tools/io-github-homenshum-nodebench/thompson-write.md
What thompson_write does on Nodebench
AI agents use thompson_write to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why thompson_write is rated Medium
This tool transforms and structures existing content into a new format (Thompson Protocol) and returns processed data. It is a content transformation and generation tool with no destructive, financial, or execution side effects. The output is data that can be edited, discarded, or regenerated, making it reversible.
From the tool's definition Tool name 'thompson_write' and description explicitly states it 'Transform[s] complex content into Thompson Protocol format' and 'Returns structured sections' — operations that create or modify formatted data outputs reversibly.
Attacks that exploit this kind of access
The rule that runs thompson_write safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For thompson_write, this is the rule to start with:
thompson_write stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every thompson_write call is checked against it from then on.
Questions about thompson_write
Transform complex content into Thompson Protocol format — plain English mandate, intuition-before-mechanics, analogy-per-concept. Returns structured sections with jargon translations and readability scores. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for thompson_write: 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 Nodebench. Nothing to install.
thompson_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the thompson_write 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.
Set action: deny in the PolicyLayer policy for thompson_write. 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.
thompson_write is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue