AI agents call get_nomenclatures to retrieve information from Oblio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reference/lookup data (nomenclatures) without modifying or deleting anything. It is a read-only operation that queries static reference information like categories, units, or tax codes. No data is created, modified, deleted, or financial operations are performed. This is a standard Read category tool with low severity since nomenclature data is typically non-sensitive reference information.
From the tool's definition Tool name 'get_nomenclatures' and description indicate it 'Fetches reference/lookup data from Oblio via GET /api/nomenclature/{type}'. The GET HTTP method and 'Fetches' language confirm data retrieval with no side effects.
Attacks that exploit this kind of access
Fetches reference/lookup data from Oblio via GET /api/nomenclature/{type}. Types and their returns:\n. It is categorised as a Read tool in the Oblio MCP Server, which means it retrieves data without modifying state.
Register the Oblio MCP server in PolicyLayer and add a rule for get_nomenclatures: 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 Oblio. Nothing to install.
get_nomenclatures 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 get_nomenclatures 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 get_nomenclatures. 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.
get_nomenclatures is provided by the Oblio MCP server (valentinludu/oblio-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 →