check_download_result_status
AI agents call check_download_result_status to retrieve information from Rodin Gen-2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool checks status of an existing download result, which is a read-only query operation with no side effects. No data is created, modified, deleted, or executed. The empty description lowers confidence slightly, but the naming pattern and server context (a 3D model generation API) clearly position this as a status-checking utility typical of async job workflows.
From the tool's definition Tool name 'check_download_result_status' and context of sibling tools (download_result, check_task_status) indicate this queries the status of a download operation without modifying state.
Attacks that exploit this kind of access
check_download_result_status. It is categorised as a Read tool in the Rodin Gen-2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rodin Gen-2 MCP Server MCP server in PolicyLayer and add a rule for check_download_result_status: 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 Rodin Gen-2 MCP Server. Nothing to install.
check_download_result_status 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 check_download_result_status 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 check_download_result_status. 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.
check_download_result_status is provided by the Rodin Gen-2 MCP Server MCP server (tigrondev/rodingen2mcp). 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 →