Get full details of a tokenized object — its properties, ownership, faces, actions, and metadata.
AI agents call dual_get_object to retrieve information from DUAL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about a tokenized object (its properties, ownership, faces, actions, and metadata) without creating, modifying, deleting, or executing any operations. It is a read-only data retrieval operation with no capability to alter blockchain state or trigger external actions.
From the tool's definition Tool name 'dual_get_object' and description 'Get full details of a tokenized object' indicate a retrieval operation with no mutation or side effects. The verb 'Get' and the phrase 'full details' clearly denote a query/fetch action.
Attacks that exploit this kind of access
Get full details of a tokenized object — its properties, ownership, faces, actions, and metadata. It is categorised as a Read tool in the DUAL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_get_object: 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 DUAL MCP Server. Nothing to install.
dual_get_object 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 dual_get_object 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 dual_get_object. 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.
dual_get_object is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). 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 →