List all available tags in the open data portal
AI agents call list_tags to retrieve information from Stefanoamorelli Rik without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available tags in a public data portal. It performs a read-only query with no ability to modify data, execute commands, or trigger external operations. The blast radius if misused is minimal—an AI agent querying tags poses no security or privacy risk. Given the context of a business register API, listing publicly available tags is a low-risk informational operation.
From the tool's definition Tool name is 'list_tags' and description states it 'List all available tags in the open data portal' — a pure retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
List all available tags in the open data portal. It is categorised as a Read tool in the Stefanoamorelli Rik MCP Server, which means it retrieves data without modifying state.
Register the Stefanoamorelli Rik MCP server in PolicyLayer and add a rule for list_tags: 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 Stefanoamorelli Rik. Nothing to install.
list_tags 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 list_tags 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 list_tags. 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.
list_tags is provided by the Stefanoamorelli Rik MCP server (@iflow-mcp/stefanoamorelli-rik-mcp-server). 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 →