Find documents related to a given document through links, backlinks, or category.
AI agents call get_related to retrieve information from Azgaarnoth MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and retrieves existing relationship metadata (links, backlinks, category associations) from the D&D world repository without creating, modifying, deleting, or executing anything. It is consistent with other Read-category sibling tools like search_world, get_document, and browse_category. No destructive or side-effect operations are possible.
From the tool's definition Tool description states it 'Find[s] documents related to a given document through links, backlinks, or category' — a retrieval/query operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Find documents related to a given document through links, backlinks, or category. It is categorised as a Read tool in the Azgaarnoth MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azgaarnoth MCP Server MCP server in PolicyLayer and add a rule for get_related: 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 Azgaarnoth MCP Server. Nothing to install.
get_related 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_related 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_related. 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_related is provided by the Azgaarnoth MCP Server MCP server (thomasserio/azgaarnoth-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 →