AI agents call ifc_get_inheritance to retrieve information from Ifc Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves structural metadata about IFC entity hierarchies from the IFC4.3 specification reference. It performs read-only lookups of inheritance relationships without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent can only read specification data that is already public and static.
From the tool's definition Tool description states it 'Get[s] the inheritance hierarchy' and 'Shows ancestor chain' and 'descendant tree' of IFC entities. These are retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Get the inheritance hierarchy of an IFC4.3 entity. Shows ancestor chain (supertypes up to IfcRoot) and/or descendant tree (subtypes). Args: - name (string): IFC entity name (e.g. It is categorised as a Read tool in the Ifc Core MCP Server, which means it retrieves data without modifying state.
Register the Ifc Core MCP server in PolicyLayer and add a rule for ifc_get_inheritance: 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 Ifc Core. Nothing to install.
ifc_get_inheritance 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 ifc_get_inheritance 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 ifc_get_inheritance. 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.
ifc_get_inheritance is provided by the Ifc Core MCP server (shuji-bonji/ifc-core-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 →