Use this before creating, modifying or reviewing XRC/XDaLa artifacts.
AI agents call get_xdala_authoring_rules 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 authoring rules for reference purposes. It has no side effects—it does not create, modify, delete, execute code, or commit financial transactions. It is a straightforward data retrieval operation used to inform subsequent decision-making. Even though it supports a workflow that may lead to Write or Execute actions, the tool itself only reads data.
From the tool's definition Tool name and description indicate it retrieves or queries XRC/XDaLa artifact rules ('Use this before creating, modifying or reviewing').
Attacks that exploit this kind of access
Use this before creating, modifying or reviewing XRC/XDaLa artifacts. 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_xdala_authoring_rules: 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_xdala_authoring_rules 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_xdala_authoring_rules 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_xdala_authoring_rules. 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_xdala_authoring_rules 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 →