get_store

One listing's full settings: price, payout wallets, preview paths, whether a GitHub key is on file.

SERVERMcp SOURCEhttps://gitbuyer.com/mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-gitbuyer-mcp/get-store.md

WHAT IT DOES

What get_store does on Mcp

AI agents call get_store to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`repo`	string	Yes
`owner`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_store is rated Low

Even though get_store only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_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 get_store, this is the rule to start with:

get_store Allowed

get_store is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_store": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every get_store call is checked against it from then on.

FAQ

Questions about get_store

What does the get_store tool do? +

One listing's full settings: price, payout wallets, preview paths, whether a GitHub key is on file. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_store accept? +

get_store accepts 2 parameters: repo, owner. 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 get_store? +

Register the MCP server in PolicyLayer and add a rule for get_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 get_store? +

get_store is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_store? +

Yes. Add a rate_limit block to the get_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 get_store completely? +

Set action: deny in the PolicyLayer policy for get_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 get_store? +

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 16 tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →