tag_search
Find all actors with a specific gameplay tag.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/tag-search.md
What tag_search does on Uefn
AI agents call tag_search to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why tag_search is rated Low
This tool performs a search operation to locate actors matching criteria, which is a read-only retrieval operation with no side effects. The verb 'find' and the search pattern align with the Read category. No data is modified, created, or destroyed. Severity is low because misuse (e.g., searching for non-existent tags) would only return results without causing harm.
From the tool's definition Tool name 'tag_search' and description 'Find all actors with a specific gameplay tag' indicate a query/search operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs tag_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tag_search, this is the rule to start with:
tag_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every tag_search call is checked against it from then on.
Questions about tag_search
Find all actors with a specific gameplay tag. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for tag_search: 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 Uefn. Nothing to install.
tag_search 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 tag_search 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 tag_search. 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.
tag_search is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue