This record as markdown: /tools/io-github-portel-dev-ncp/post-data.md
What post_data does on Ncp
AI agents use post_data 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 post_data is rated Medium
This tool creates new data (posts/tweets) on Twitter, which is a reversible write operation. While it modifies external state, tweets can be deleted, making it Write rather than Destructive. Severity is medium because misuse could spam, harass, or damage reputation, but the blast radius is limited to the Twitter account's reach and can be remediated by deletion.
From the tool's definition Tool name is 'post_data' and description states it 'Send[s] data to twitter-api-v2', indicating it creates or posts content to an external service.
Attacks that exploit this kind of access
The rule that runs post_data 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 post_data, this is the rule to start with:
post_data 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 post_data call is checked against it from then on.
Questions about post_data
Send data to twitter-api-v2. 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 post_data: 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.
post_data 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 post_data 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 post_data. 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.
post_data 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