Low Risk

get_shop_details

Get store details from tokopedia by product_url or shop_url. Get product_url from search_product tool or shop_url from search_shop tool.

How to control get_shop_details ↓

AI agents call get_shop_details to retrieve information from Get Gather without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and queries publicly available store information from Tokopedia based on provided URLs. It has no side effects, does not modify data, execute code, or perform financial operations. It falls squarely into the Read category with low severity since data retrieval alone poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_shop_details' and description indicate retrieval of store details from Tokopedia via URL parameters. No modification, deletion, code execution, or financial transactions are performed.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_shop_details": {}
  }
}

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

  1. Create a free account and register Get Gather — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_shop_details tool do? +

Get store details from tokopedia by product_url or shop_url. Get product_url from search_product tool or shop_url from search_shop tool. It is categorised as a Read tool in the Get Gather MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_shop_details? +

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

What risk level is get_shop_details? +

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

Can I rate-limit get_shop_details? +

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

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

get_shop_details is provided by the Get Gather MCP server (remotebrowser/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Get Gather tool call.

Deterministic rules across all 62 Get Gather tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

62 Get Gather tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.