get_item_detail

THE RISK

Low Risk

Why get_item_detail needs a policy

This tool queries and retrieves structured item details from Goofish (a Chinese marketplace platform) without creating, modifying, deleting, or executing operations. It is a straightforward read operation with no side effects. Severity is low because misuse would only expose marketplace item data already accessible via the platform.

From the tool's definition Tool description states 'Get Goofish/Xianyu item detail by item_id or URL' — retrieves item details with no modification capability.

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

POLICY

How to control get_item_detail

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

policy.json

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

get_item_detail 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 Goofish MCP Server — 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 Goofish MCP Server tools

Write publish_item Publish a new Goofish/Xianyu second-hand item listing. Read monitor_keyword Return a normalized Goofish/Xianyu keyword snapshot for monitoring. Read search_items Search Goofish/Xianyu items by keyword using a logged-in Playwright browser context. Examp

All 4 Goofish MCP Server 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_item_detail

What does the get_item_detail tool do? +

Get Goofish/Xianyu item detail by item_id or URL. It is categorised as a Read tool in the Goofish MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_item_detail? +

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

What risk level is get_item_detail? +

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

Can I rate-limit get_item_detail? +

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

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

get_item_detail is provided by the Goofish MCP Server MCP server (mercy719/goofish-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Goofish MCP Server tool call.

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

CHECK YOUR STACK →