Low Risk

get_field_definition

Get field details

Part of the U2 MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

u2-mcp Read Risk 2/5

AI agents call get_field_definition to retrieve information from U2 MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_field_definition only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

u2-mcp-server.yaml
tools:
  get_field_definition:
    rules:
      - action: allow

See the full U2 MCP Server policy for all 22 tools.

Tool Name get_field_definition
Category Read
Risk Level Low

View all 22 tools →

Agents calling read-class tools like get_field_definition have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_field_definition tool do? +

Get field details. It is categorised as a Read tool in the U2 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_field_definition? +

Add a rule in your Intercept YAML policy under the tools section for get_field_definition. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the U2 MCP Server MCP server.

What risk level is get_field_definition? +

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

Can I rate-limit get_field_definition? +

Yes. Add a rate_limit block to the get_field_definition rule in your Intercept 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_field_definition completely? +

Set action: deny in the Intercept policy for get_field_definition. 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_field_definition? +

get_field_definition is provided by the U2 MCP Server MCP server (u2-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on U2 MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.