probe_clean

Probe-as-service signal: return Dual clean-registry status. Fail deposits danger pheromone; ok dampens danger.

SERVERDual Registry SOURCEhttps://www.dualregistry.dev/api/protocol

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-dualregistry-registry/probe-clean.md

WHAT IT DOES

What probe_clean does on Dual Registry

AI agents call probe_clean to retrieve information from Dual Registry without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required
`id`	string	—
`name`	string	—
`listing_id`	string	—

Parameters from the server's own tool schema.

RISK

Why probe_clean is rated Low

Even though probe_clean only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs probe_clean safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For probe_clean, this is the rule to start with:

probe_clean Allowed

probe_clean is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "probe_clean": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dual Registry, apply this rule, and every probe_clean call is checked against it from then on.

FAQ

Questions about probe_clean

What does the probe_clean tool do? +

Probe-as-service signal: return Dual clean-registry status. Fail deposits danger pheromone; ok dampens danger. It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.

What parameters does probe_clean accept? +

probe_clean accepts 3 parameters: id, name, listing_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on probe_clean? +

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

What risk level is probe_clean? +

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

Can I rate-limit probe_clean? +

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

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

probe_clean is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dual Registry, and thousands of servers like it.

This server

All 64 Dual Registry tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →