Low Risk

get_ui_reference

get_ui_reference

How to control get_ui_reference ↓

AI agents call get_ui_reference to retrieve information from Proxima without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Based on naming convention and context within a set of primarily Read and Execute tools on an AI gateway server, 'get_ui_reference' most likely retrieves UI reference documentation or specifications without side effects. No evidence suggests modification, deletion, or external execution.

From the tool's definition Tool name 'get_ui_reference' suggests retrieval of UI documentation or reference material. The pattern matches sibling tools like 'analyze_document' and 'academic_search' which are informational read operations.

Documented attack patterns abuse exactly the kind of access get_ui_reference gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Proxima, and nothing reaches the server without passing your rules. This is the rule we recommend for get_ui_reference:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_ui_reference": {}
  }
}

get_ui_reference is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Proxima — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_ui_reference tool do? +

get_ui_reference. It is categorised as a Read tool in the Proxima MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ui_reference? +

Register the Proxima MCP server in PolicyLayer and add a rule for get_ui_reference: 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 Proxima. Nothing to install.

What risk level is get_ui_reference? +

get_ui_reference is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_ui_reference? +

Yes. Add a rate_limit block to the get_ui_reference 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.

How do I block get_ui_reference completely? +

Set action: deny in the PolicyLayer policy for get_ui_reference. 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.

What MCP server provides get_ui_reference? +

get_ui_reference is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proxima tool call.

Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

50 Proxima tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.