Low Risk

discover

Show which quality dimensions matter for a stated purpose, WITHOUT ranking any models. Returns the inferred weights and the discovery-walk trace. Useful for understanding how XFMS interprets the purpose before committing to a pick.

Part of the XFMS — Model Source server.

discover is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE XFMS — MODEL SOURCE →

Free to start. No card required.

AI agents call discover to retrieve information from XFMS — Model Source 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 discover 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.

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

See the full XFMS — Model Source policy for all 5 tools.

Get this rule live on your own XFMS — Model Source server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY XFMS — MODEL SOURCE →

These attack patterns abuse exactly the kind of access discover gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so discover only ever does what you allow.

SECURE XFMS — MODEL SOURCE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the discover tool do? +

Show which quality dimensions matter for a stated purpose, WITHOUT ranking any models. Returns the inferred weights and the discovery-walk trace. Useful for understanding how XFMS interprets the purpose before committing to a pick.. It is categorised as a Read tool in the XFMS — Model Source MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on discover? +

Register the XFMS — Model Source MCP server in PolicyLayer and add a rule for discover: 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 XFMS — Model Source. Nothing to install.

What risk level is discover? +

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

Can I rate-limit discover? +

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

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

discover is provided by the XFMS — Model Source MCP server (https://xfms.vercel.app/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every XFMS — Model Source tool call.

Deterministic rules across all 5 XFMS — Model Source tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.