update_store
Edit a listing without re-listing it: reprice, rewallet, rekey, or change preview paths. Only the fields you send change; the old checkout is voided so stale links stop selling.
This record as markdown: /tools/com-gitbuyer-mcp/update-store.md
What update_store does on Mcp
AI agents use update_store to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | |
owner | string | Yes | |
price_usd | string | — | |
github_pat | string | — | new key; empty string clears |
wallet_base | string | — | |
preview_paths | array | — | |
wallet_solana | string | — |
Parameters from the server's own tool schema.
Why update_store is rated Medium
An AI agent can call update_store faster than any human can review: one bad instruction and it creates or modifies resources in Mcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_store safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_store, this is the rule to start with:
update_store 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 Mcp, apply this rule, and every update_store call is checked against it from then on.
Questions about update_store
Edit a listing without re-listing it: reprice, rewallet, rekey, or change preview paths. Only the fields you send change; the old checkout is voided so stale links stop selling. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_store accepts 7 parameters: repo, owner, price_usd, github_pat, wallet_base, preview_paths, wallet_solana. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for update_store: 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 Mcp. Nothing to install.
update_store 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 update_store 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 update_store. 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.
update_store is provided by the MCP server (https://gitbuyer.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue