Read-only list of indexed OSTC state entries for an XRC-729 contract.
AI agents call get_xrc729_ostc_state to retrieve information from XGR MCP Gateway 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 blockchain state data without modification, deletion, or execution of transactions. It performs a simple data lookup operation on an XRC-729 contract's OSTC state, which is a classic Read operation. No financial transactions, destructive operations, or code execution are involved.
From the tool's definition Tool description explicitly states 'Read-only list of indexed OSTC state entries for an XRC-729 contract.' The 'Read-only' designation and 'list' operation are clear indicators of retrieval with no side effects.
Attacks that exploit this kind of access
Read-only list of indexed OSTC state entries for an XRC-729 contract. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for get_xrc729_ostc_state: 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 XGR MCP Gateway. Nothing to install.
get_xrc729_ostc_state 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 get_xrc729_ostc_state 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 get_xrc729_ostc_state. 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.
get_xrc729_ostc_state is provided by the XGR MCP Gateway MCP server (xgr-network/xgr-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 →