This record as markdown: /tools/io-github-portel-dev-ncp/write-sheet.md
What write_sheet does on Ncp
AI agents use write_sheet to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why write_sheet is rated Medium
This tool creates or modifies data in Google Sheets, which is reversible (data can be edited or undone). It does not delete data irreversibly, execute arbitrary code, or commit financial transactions. The medium severity reflects that unauthorized writes to shared sheets could corrupt data or disrupt workflows, but the impact is limited to one service and reversible.
From the tool's definition Tool name is 'write_sheet' and description states 'Write data to Google Sheets'. The verb 'write' explicitly indicates data modification.
Attacks that exploit this kind of access
The rule that runs write_sheet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For write_sheet, this is the rule to start with:
write_sheet 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 Ncp, apply this rule, and every write_sheet call is checked against it from then on.
Questions about write_sheet
Write data to Google Sheets. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for write_sheet: 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 Ncp. Nothing to install.
write_sheet 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 write_sheet 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 write_sheet. 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.
write_sheet is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue