Low Risk

describe_tool

Get details about a specific tool (parameters, description, category).

How to control describe_tool ↓

What describe_tool does on Uefn

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

Low Risk

Why describe_tool needs a policy

This is a read-only information retrieval operation. It fetches and returns tool metadata (parameters, description, category) with no side effects on the UEFN editor state, assets, or any other system. The minimal blast radius and passive nature of querying tool information justifies a 'low' severity classification.

From the tool's definition Tool name 'describe_tool' and description 'Get details about a specific tool (parameters, description, category)' indicate a retrieval operation that queries and returns metadata about tools without modifying, executing, or deleting anything.

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

How to control describe_tool

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

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

describe_tool 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 Uefn — 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.

Related tools and policies

Go deeper

Questions about describe_tool

What does the describe_tool tool do? +

Get details about a specific tool (parameters, description, category). It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_tool? +

Register the Uefn MCP server in PolicyLayer and add a rule for describe_tool: 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.

What risk level is describe_tool? +

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

Can I rate-limit describe_tool? +

Yes. Add a rate_limit block to the describe_tool 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 describe_tool completely? +

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

describe_tool 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.

Enforce policy on every Uefn tool call.

Start from Uefn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

143 Uefn tools catalogued and risk-classified — across an index of 43,000+ 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.