Get class inheritance hierarchy and modded extensions
AI agents call get_class_hierarchy to retrieve information from DayZ API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns structural information about the DayZ API's class hierarchy. It has no side effects, does not modify data, does not execute code, and does not affect external systems. It is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool retrieves class inheritance hierarchy and modded extensions information. The verb 'Get' and the nature of the function—providing metadata about class structures—indicate data retrieval with no modification, deletion, or code execution capabilities.
Attacks that exploit this kind of access
Get class inheritance hierarchy and modded extensions. It is categorised as a Read tool in the DayZ API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DayZ API MCP Server MCP server in PolicyLayer and add a rule for get_class_hierarchy: 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 DayZ API MCP Server. Nothing to install.
get_class_hierarchy 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_class_hierarchy 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_class_hierarchy. 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_class_hierarchy is provided by the DayZ API MCP Server MCP server (quantumloader/dayz-api-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 →