detect_projects

A read tool on the Metis Public Health MCP server.

SERVERMetis Public Health SOURCEsveritg/metis_ph

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sveritg-metis-ph/detect-projects.md

WHAT IT DOES

What detect_projects does on Metis Public Health

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

RISK

Why detect_projects is rated Low

The tool name 'detect_projects' suggests information retrieval or discovery functionality. Without a description, confidence is moderate. The absence of action verbs like 'create', 'delete', 'execute', or 'run' suggests non-destructive analysis. Sibling tools are predominantly read/write operations (memory entries, glossary terms), and this fits the pattern of a discovery/query tool.

From the tool's definition Tool named 'detect_projects' with no description provided. Based on naming convention and the server's context as a research companion that indexes and retrieves information, this tool likely detects or identifies projects from indexed data without modifying…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs detect_projects safely

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

detect_projects Allowed

detect_projects 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": {
    "detect_projects": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every detect_projects call is checked against it from then on.

FAQ

Questions about detect_projects

What does the detect_projects tool do? +

detect_projects is a read tool on the Metis Public Health MCP server. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on detect_projects? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for detect_projects: 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 Metis Public Health. Nothing to install.

What risk level is detect_projects? +

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

Can I rate-limit detect_projects? +

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

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

detect_projects is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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