Replace ALL content of one of YOUR repositories with the provided body. This is a FULL REPLACE, not a partial merge — any file you omit is DELETED. To change part of a repo, first call prompthub_get_repo, edit the returned fields, then send the COMPLETE set back (map the returned
AI agents use prompthub_update_repo to create or update resources in Prompthub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prompthub environment.
While the primary action is replacing/updating repository content (Write), the mechanism includes automatic deletion of omitted files, which borders on destructive. However, since the deletions are secondary to the primary write operation and the user has full control by providing the complete set of files, this is classified as Write rather than Destructive.
From the tool's definition The description explicitly states 'Replace ALL content' and 'FULL REPLACE, not a partial merge — any file you omit is DELETED.' This indicates the tool modifies repository content, including deletion of omitted files as a side effect.
Attacks that exploit this kind of access
Replace ALL content of one of YOUR repositories with the provided body. This is a FULL REPLACE, not a partial merge — any file you omit is DELETED. To change part of a repo, first call prompthub_get_repo, edit the returned fields, then send the COMPLETE set back (map the returned. It is categorised as a Write tool in the Prompthub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prompthub MCP server in PolicyLayer and add a rule for prompthub_update_repo: 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 Prompthub. Nothing to install.
prompthub_update_repo 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 prompthub_update_repo 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 prompthub_update_repo. 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.
prompthub_update_repo is provided by the Prompthub MCP server (lionelhao/prompthub-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 →