将静态网站、HTML 文件或前端项目上传到 Pinme (IPFS)。支持单个文件或整个目录。如果未指定路径,会自动检测常见的构建输出目录(build、dist、out、.next 等)。
AI agents use deploy_to_pinme to create or update resources in Pinme Deploy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pinme Deploy MCP Server environment.
This tool uploads/deploys files to an external IPFS service (Pinme). It creates new data on a remote platform — a Write operation. Severity is high because an AI agent could inadvertently deploy sensitive files or entire directories (including ones auto-detected like .next which may contain secrets or server-side code artifacts) to a public, immutable IPFS network.
From the tool's definition 将静态网站、HTML 文件或前端项目上传到 Pinme (IPFS)。支持单个文件或整个目录 (uploads static websites, HTML files or frontend projects to Pinme/IPFS, supports single files or entire directories)
Attacks that exploit this kind of access
将静态网站、HTML 文件或前端项目上传到 Pinme (IPFS)。支持单个文件或整个目录。如果未指定路径,会自动检测常见的构建输出目录(build、dist、out、.next 等)。. It is categorised as a Write tool in the Pinme Deploy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pinme Deploy MCP Server MCP server in PolicyLayer and add a rule for deploy_to_pinme: 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 Pinme Deploy MCP Server. Nothing to install.
deploy_to_pinme 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 deploy_to_pinme 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 deploy_to_pinme. 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.
deploy_to_pinme is provided by the Pinme Deploy MCP Server MCP server (liaoshengrong/pinme-deploy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →