Low Risk

get_related_items

Get all items that are related to the specified item.

Risk signalsBulk/mass operation — affects multiple targets

Part of the Caffeinated Wardrobe server.

get_related_items 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 CAFFEINATED WARDROBE →

Free to start. No card required.

AI agents call get_related_items to retrieve information from Caffeinated Wardrobe 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_related_items 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_related_items": {}
  }
}

See the full Caffeinated Wardrobe policy for all 20 tools.

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

ENFORCE ON MY CAFFEINATED WARDROBE →

View all 20 tools →

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

SECURE CAFFEINATED WARDROBE →

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

What does the get_related_items tool do? +

Get all items that are related to the specified item.. It is categorised as a Read tool in the Caffeinated Wardrobe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_related_items? +

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

What risk level is get_related_items? +

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

Can I rate-limit get_related_items? +

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

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

get_related_items is provided by the Caffeinated Wardrobe MCP server (michelle/caffeinated-wardrobe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Caffeinated Wardrobe tool call.

Deterministic rules across all 20 Caffeinated Wardrobe 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.