Low Risk

read_taxonomy

Discover how items on 1stDibs are categorized. We have a taxonomy with furniture, art, jewelry, and fashion categories at the top level. This will return a list of next level categories as well as facets with their appropriate filters. You need to specify a category.

Part of the 1stDibs server.

read_taxonomy 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 1STDIBS →

Free to start. No card required.

AI agents call read_taxonomy to retrieve information from 1stDibs 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 read_taxonomy 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": {
    "read_taxonomy": {}
  }
}

See the full 1stDibs policy for all 4 tools.

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

ENFORCE ON MY 1STDIBS →

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

SECURE 1STDIBS →

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

What does the read_taxonomy tool do? +

Discover how items on 1stDibs are categorized. We have a taxonomy with furniture, art, jewelry, and fashion categories at the top level. This will return a list of next level categories as well as facets with their appropriate filters. You need to specify a category.. It is categorised as a Read tool in the 1stDibs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_taxonomy? +

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

What risk level is read_taxonomy? +

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

Can I rate-limit read_taxonomy? +

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

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

read_taxonomy is provided by the 1stDibs MCP server (https://www.1stdibs.com/soa/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 1stDibs tool call.

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