compress_or_expand_text
Precisely compress or expand academic text by a target word count. Compress mode: remove filler words, convert clauses to phrases, passive to active. Expand mode: add logical connectors, explicit reasoning, implicit conclusions. Preserves all core information and LaTeX formatting.
This record as markdown: /tools/io-github-homenshum-nodebench/compress-or-expand-text.md
What compress_or_expand_text does on Nodebench
AI agents use compress_or_expand_text 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 compress_or_expand_text is rated Medium
This tool modifies text content by compressing or expanding it, which is a reversible write/transform operation. It does not execute code, delete data, or involve financial transactions. Severity is low as it only manipulates text provided to it.
From the tool's definition compress or expand academic text by a target word count... Preserves all core information and LaTeX formatting
Attacks that exploit this kind of access
The rule that runs compress_or_expand_text 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 compress_or_expand_text, this is the rule to start with:
compress_or_expand_text 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 compress_or_expand_text call is checked against it from then on.
Questions about compress_or_expand_text
Precisely compress or expand academic text by a target word count. Compress mode: remove filler words, convert clauses to phrases, passive to active. Expand mode: add logical connectors, explicit reasoning, implicit conclusions. Preserves all core information and LaTeX formatting. 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 compress_or_expand_text: 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.
compress_or_expand_text 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 compress_or_expand_text 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 compress_or_expand_text. 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.
compress_or_expand_text 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