Low Risk

url-metadata

Extract metadata from a URL including title, description, Open Graph data, and favicon information

Accepts URL/endpoint input (url)

Part of the DuckDuckGo & Felo AI Search MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call url-metadata to retrieve information from DuckDuckGo & Felo AI Search 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 url-metadata 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.

oevortex-ddg-search.yaml
tools:
  url-metadata:
    rules:
      - action: allow

See the full DuckDuckGo & Felo AI Search policy for all 4 tools.

Tool Name url-metadata
Category Read
Risk Level Low

Agents calling read-class tools like url-metadata 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 url-metadata tool do? +

Extract metadata from a URL including title, description, Open Graph data, and favicon information. It is categorised as a Read tool in the DuckDuckGo & Felo AI Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on url-metadata? +

Add a rule in your Intercept YAML policy under the tools section for url-metadata. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the DuckDuckGo & Felo AI Search MCP server.

What risk level is url-metadata? +

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

Can I rate-limit url-metadata? +

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

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

url-metadata is provided by the DuckDuckGo & Felo AI Search MCP server (OEvortex/ddg_search). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on DuckDuckGo & Felo AI Search

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.