This record as markdown: /tools/indigoprotocol-indigo-mcp/store-on-ipfs.md
What store_on_ipfs does on Indigo Protocol MCP
AI agents use store_on_ipfs to create or update resources in Indigo Protocol MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Indigo Protocol MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | Text content to store on IPFS |
Parameters from the server's own tool schema.
Why store_on_ipfs is rated Medium
This tool writes data to IPFS (InterPlanetary File System), a distributed storage network. It creates new content-addressed objects on a public decentralized network. While IPFS content is immutable once stored and cannot be deleted (making it somewhat irreversible), the primary action is a write/upload operation.
From the tool's definition 'Store text content on IPFS' — creates/uploads new data to IPFS storage
Attacks that exploit this kind of access
The rule that runs store_on_ipfs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store_on_ipfs, this is the rule to start with:
store_on_ipfs 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 Indigo Protocol MCP, apply this rule, and every store_on_ipfs call is checked against it from then on.
Questions about store_on_ipfs
Store text content on IPFS. It is categorised as a Write tool in the Indigo Protocol MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
store_on_ipfs accepts 1 parameter: text. The full parameter table on this page comes from the server's own tool schema.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for store_on_ipfs: 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 Indigo Protocol MCP. Nothing to install.
store_on_ipfs 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 store_on_ipfs 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 store_on_ipfs. 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.
store_on_ipfs is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indigo Protocol, and thousands of servers like it.
This server
Across the catalogue