AI agents call rucio_list_requests_history to retrieve information from Rucio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it lists historical request records from Rucio's distributed data management system. Listing and retrieving historical data constitutes a Read operation with no side effects. Given the context of sibling tools that include read operations (get_account, get_did, get_distance) and the absence of any modifying verbs (create, update, delete, approve, deny), this tool appears to be informational.
From the tool's definition Tool name contains 'list' and 'history', which are read-only operations. The prefix 'rucio_' indicates this is a Rucio data management operation. No description provided, but the naming pattern aligns with query/retrieval functions.
Attacks that exploit this kind of access
rucio_list_requests_history. It is categorised as a Read tool in the Rucio MCP Server, which means it retrieves data without modifying state.
Register the Rucio MCP server in PolicyLayer and add a rule for rucio_list_requests_history: 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 Rucio. Nothing to install.
rucio_list_requests_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rucio_list_requests_history 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.
Set action: deny in the PolicyLayer policy for rucio_list_requests_history. 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.
rucio_list_requests_history is provided by the Rucio MCP server (kratsg/rucio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →