Get full details of a specific entity by its ID.
AI agents call orion_get_entity to retrieve information from Fiware Orion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves entity details from the FIWARE Orion Context Broker without modifying, deleting, or executing any operations. It is a straightforward read operation analogous to a GET request in REST APIs. The severity is low because reading data poses minimal risk even if accessed inappropriately, though it could expose sensitive sensor or device information depending on the entity contents.
From the tool's definition Tool name 'orion_get_entity' and description 'Get full details of a specific entity by its ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get full details of a specific entity by its ID. It is categorised as a Read tool in the Fiware Orion MCP Server, which means it retrieves data without modifying state.
Register the Fiware Orion MCP server in PolicyLayer and add a rule for orion_get_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 Fiware Orion. Nothing to install.
orion_get_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 orion_get_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 orion_get_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.
orion_get_entity is provided by the Fiware Orion MCP server (k2iser/fiware-orion-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 →