This record as markdown: /tools/quangdang46-uefn-verse-mcp/proximity-find.md
What proximity_find does on Uefn
AI agents call proximity_find 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 proximity_find is rated Low
The tool name indicates a search/query operation that retrieves data about objects in proximity to a location or actor, with no indication of modification, execution, deletion, or financial impact. However, confidence is moderate (0.7) rather than high because the description is empty, preventing confirmation of exact behavior and whether it has any side effects.
From the tool's definition Tool name 'proximity_find' suggests querying or searching for nearby objects/actors based on spatial proximity. Naming convention (noun + 'find') is consistent with Read operations like 'audio_list' on the same server.
Attacks that exploit this kind of access
The rule that runs proximity_find 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 proximity_find, this is the rule to start with:
proximity_find 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 proximity_find call is checked against it from then on.
Questions about proximity_find
proximity_find is a read tool on the Uefn MCP server. 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 proximity_find: 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.
proximity_find 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 proximity_find 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 proximity_find. 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.
proximity_find 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