Retrieve machine-readable JSON schema for XGR standards.
AI agents call get_xgr_standard_schema 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 performs a straightforward query operation to fetch schema definitions, similar to documentation or metadata retrieval. There is no modification, deletion, execution of code, or financial impact. The confidence is high (0.95) because the description is clear and unambiguous about the retrieval nature of the operation.
From the tool's definition Tool retrieves and returns machine-readable JSON schema for XGR standards. The verb 'Retrieve' combined with the fact that this is schema introspection indicates read-only data access with no side effects.
Attacks that exploit this kind of access
Retrieve machine-readable JSON schema for XGR standards. 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_xgr_standard_schema: 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_xgr_standard_schema 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_xgr_standard_schema 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_xgr_standard_schema. 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_xgr_standard_schema 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 →