Query Omnibus delay status for specific article (e.g., 'Article 11').
AI agents call query_article to retrieve information from MEOK Omnibus Tracker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about EU AI Act article compliance status from a tracker. It performs a lookup/fetch operation without modifying, executing, or deleting any data. The low severity reflects that misuse would only expose informational data about regulatory status, with no destructive or operational consequences.
From the tool's definition Tool name 'query_article' and description 'Query Omnibus delay status for specific article' indicate data retrieval with no side effects. The verb 'query' combined with 'status' retrieval confirms read-only operation.
Attacks that exploit this kind of access
Query Omnibus delay status for specific article (e.g., 'Article 11'). It is categorised as a Read tool in the MEOK Omnibus Tracker MCP Server, which means it retrieves data without modifying state.
Register the MEOK Omnibus Tracker MCP server in PolicyLayer and add a rule for query_article: 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 MEOK Omnibus Tracker. Nothing to install.
query_article 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 query_article 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 query_article. 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.
query_article is provided by the MEOK Omnibus Tracker MCP server (pypi:meok-omnibus-tracker-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 →