get_store_info

THE RISK

Low Risk

Why get_store_info needs a policy

This tool retrieves read-only store configuration data without side effects. It poses minimal risk as it only exposes general store metadata that is typically non-sensitive or already known to authorized users. Blast radius is low since misuse merely provides information about the store, not access to sensitive customer/order data or ability to modify systems.

From the tool's definition Tool description states 'Get Sapo store information' with retrieval of static metadata (name, domain, address, currency, timezone, owner). No modification, deletion, or execution indicated.

Documented attack patterns abuse exactly the kind of access get_store_info gives an agent:

POLICY

How to control get_store_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Sapo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_store_info:

policy.json

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

get_store_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Sapo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sapo tools

Financial create_order_transaction Create a transaction for an order (e.g. capture, sale, refund). Side effect: creates a Tra Execute create_script_tag Inject a new JavaScript file into the storefront. For SEO/content team: Execute send_draft_order_invoice Send an invoice email for a draft order. Side effect: sends email to customer; draft statu Write adjust_inventory_level Adjust inventory level by a relative delta (positive = receive stock, negative = remove st Write add_customer_address Add a new address to a customer. Required: address1, city, country. Write complete_draft_order Complete a draft order and convert it into a real order. Side effect: creates an Order fro Write connect_inventory_level Connect an inventory item to a location (enable tracking at that location). For store owne Write create_article Create a new article within a blog. For SEO/content team: provide title, HTML body,

All 93 Sapo tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_store_info

What does the get_store_info tool do? +

Get Sapo store information: name, domain, address, currency, timezone, owner. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_store_info? +

Register the Sapo MCP server in PolicyLayer and add a rule for get_store_info: 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 Sapo. Nothing to install.

What risk level is get_store_info? +

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

Can I rate-limit get_store_info? +

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

Set action: deny in the PolicyLayer policy for get_store_info. 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_info? +

get_store_info is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sapo tool call.

Start from Sapo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →