Search IFC4.3 entities by name or description keyword. Returns matching entities with their name, layer, schema, and short definition. Supports partial name matching and description text search. Args: - query (string): Search keyword (e.g.
AI agents call ifc_search_entity 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 performs a search and retrieval operation against the IFC4.3 specification database. It queries entity definitions using keywords and returns matching results. There are no side effects, data modifications, code execution, or financial implications. The search functionality is purely informational and aligns with the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool description explicitly states 'Search IFC4.3 entities' and 'Returns matching entities with their name, layer, schema, and short definition.' The operations are read-only queries with no modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
Search IFC4.3 entities by name or description keyword. Returns matching entities with their name, layer, schema, and short definition. Supports partial name matching and description text search. Args: - query (string): Search keyword (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_search_entity: 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_search_entity 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_search_entity 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_search_entity. 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_search_entity 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 →