Low Risk

urdb_get_product

Get full integrity breakdown for a specific product — scores across 7 dimensions (durability, repairability, material quality, version stability, anti-shrinkflation, firmware lock-in, ownership integrity), plus change event and recall counts.

Part of the Urdb server.

urdb_get_product 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 URDB →

Free to start. No card required.

AI agents call urdb_get_product to retrieve information from Urdb 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 urdb_get_product 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": {
    "urdb_get_product": {}
  }
}

See the full Urdb policy for all 4 tools.

Get this rule live on your own Urdb server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY URDB →

These attack patterns abuse exactly the kind of access urdb_get_product 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 urdb_get_product only ever does what you allow.

SECURE URDB →

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

What does the urdb_get_product tool do? +

Get full integrity breakdown for a specific product — scores across 7 dimensions (durability, repairability, material quality, version stability, anti-shrinkflation, firmware lock-in, ownership integrity), plus change event and recall counts.. It is categorised as a Read tool in the Urdb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on urdb_get_product? +

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

What risk level is urdb_get_product? +

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

Can I rate-limit urdb_get_product? +

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

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

urdb_get_product is provided by the Urdb MCP server (urdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Urdb tool call.

Deterministic rules across all 4 Urdb 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.