New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERMcp SOURCEhttps://gitbuyer.com/mcp
Medium RISK CLASS
Category Write
Parameters 72 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about update_store

What does the update_store tool do? +

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.

What parameters does update_store accept? +

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.

How do I enforce a policy on update_store? +

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.

What risk level is update_store? +

update_store is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_store? +

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.

How do I block update_store completely? +

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.

What MCP server provides update_store? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.