This record as markdown: /tools/io-github-portel-dev-ncp/add-document.md
What add_document does on Ncp
AI agents use add_document 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 add_document is rated Medium
This tool creates or adds new documents to a Firestore database, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because unauthorized document creation could pollute a database or cause application issues, but the operation is reversible through deletion or updates.
From the tool's definition Tool name 'add_document' combined with description 'Add document to Firestore' indicates creation of new data in a Firestore database.
Attacks that exploit this kind of access
The rule that runs add_document 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 add_document, this is the rule to start with:
add_document 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 add_document call is checked against it from then on.
Questions about add_document
Add document to Firestore. 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 add_document: 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.
add_document 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 add_document 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 add_document. 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.
add_document 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