Low Risk

get_product_detail

获取单个产品的结构化信息。compact=true时只返回摘要字段,适合Agent快速浏览;默认返回完整信息含条款详情。

Part of the WhyLingxi 保险顾问 Insurance Advisor server.

get_product_detail is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE WHYLINGXI 保险顾问 INSURANCE ADVISOR →

Free to start. No card required.

AI agents call get_product_detail to retrieve information from WhyLingxi 保险顾问 Insurance Advisor without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_product_detail only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full WhyLingxi 保险顾问 Insurance Advisor policy for all 9 tools.

Get this rule live on your own WhyLingxi 保险顾问 Insurance Advisor server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WHYLINGXI 保险顾问 INSURANCE ADVISOR →

View all 9 tools →

These attack patterns abuse exactly the kind of access get_product_detail gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_product_detail only ever does what you allow.

SECURE WHYLINGXI 保险顾问 INSURANCE ADVISOR →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_product_detail tool do? +

获取单个产品的结构化信息。compact=true时只返回摘要字段,适合Agent快速浏览;默认返回完整信息含条款详情。. It is categorised as a Read tool in the WhyLingxi 保险顾问 Insurance Advisor MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_product_detail? +

Register the WhyLingxi 保险顾问 Insurance Advisor MCP server in PolicyLayer and add a rule for get_product_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 WhyLingxi 保险顾问 Insurance Advisor. Nothing to install.

What risk level is get_product_detail? +

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

Can I rate-limit get_product_detail? +

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

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

get_product_detail is provided by the WhyLingxi 保险顾问 Insurance Advisor MCP server (https://whylingxi.cn/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WhyLingxi 保险顾问 Insurance Advisor tool call.

Deterministic rules across all 9 WhyLingxi 保险顾问 Insurance Advisor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.