quantumleap_get_type_history
AI agents call quantumleap_get_type_history 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.
The tool appears to fetch historical time-series data from QuantumLeap (FIWARE's time-series database) filtered by entity type. This is a retrieval operation with no side effects on the underlying data. Confidence is lowered from 0.9 to 0.85 due to the empty description, but the naming pattern and sibling context strongly suggest read-only semantics.
From the tool's definition Tool name 'quantumleap_get_type_history' suggests retrieval of historical data by type. The 'get_' prefix and 'history' suffix indicate a read-only query operation.
Attacks that exploit this kind of access
quantumleap_get_type_history. 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 quantumleap_get_type_history: 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.
quantumleap_get_type_history 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 quantumleap_get_type_history 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 quantumleap_get_type_history. 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.
quantumleap_get_type_history 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 →