get_inbox_item_details

THE RISK

Low Risk

Why get_inbox_item_details needs a policy

This tool retrieves and queries existing inbox item data from the RAD Security API. The 'get' prefix and passive retrieval nature confirm it is a Read operation. No data is modified, deleted, executed, or created. The blast radius is minimal as it only exposes existing security findings or reports already in the system. Low severity is appropriate for read-only access to security metadata.

From the tool's definition Tool name 'get_inbox_item_details' uses the 'get' verb and description states 'Get detailed information about a specific inbox item', indicating retrieval of existing data without modification or side effects.

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

POLICY

How to control get_inbox_item_details

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

policy.json

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

get_inbox_item_details 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 RAD Security — 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 RAD Security tools

Execute run_workflow Run a workflow with optional argument overrides Execute radql_batch_query Execute multiple RadQL queries in parallel for efficiency. Useful for fetching related dat Execute radql_query_builder Helper tool to build RadQL queries programmatically from structured conditions. Useful whe Write add_workflow_schedule Add a cron-based schedule to a workflow. The schedule will trigger the workflow automatica Write create_custom_workflow Create a new custom workflow from YAML definition. The YAML will be validated before deplo Write mark_inbox_item_as_false_positive Mark an inbox item as a false positive with a reason Write update_custom_workflow Update an existing custom workflow with new YAML. Only custom workflows (created via creat Write update_security_finding_status Update the status of a security finding

All 55 RAD Security 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_inbox_item_details

What does the get_inbox_item_details tool do? +

Get detailed information about a specific inbox item. It is categorised as a Read tool in the RAD Security MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_inbox_item_details? +

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

What risk level is get_inbox_item_details? +

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

Can I rate-limit get_inbox_item_details? +

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

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

get_inbox_item_details is provided by the RAD Security MCP server (rad-security/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 RAD Security tool call.

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

CHECK YOUR STACK →