This record as markdown: /tools/io-github-portel-dev-ncp/sync-base.md
What sync_base does on Ncp
AI agents use sync_base 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 sync_base is rated Medium
The tool performs data synchronization, which creates or modifies records reversibly in Airtable. This is a Write operation with high severity due to potential for large-scale unintended data modifications if the external data source or sync configuration is malicious or misconfigured.
From the tool's definition Tool description states 'Synchronize Airtable base with external data' — synchronization implies modifying/updating data in the target Airtable base based on external source data.
Attacks that exploit this kind of access
The rule that runs sync_base 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 sync_base, this is the rule to start with:
sync_base 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 sync_base call is checked against it from then on.
Questions about sync_base
Synchronize Airtable base with external data. 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 sync_base: 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.
sync_base 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 sync_base 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 sync_base. 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.
sync_base 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