scan_project_scripts
A execute tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/scan-project-scripts.md
What scan_project_scripts does on Metis Public Health
AI agents invoke scan_project_scripts to trigger actions in Metis Public Health. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why scan_project_scripts is rated High
The name suggests this tool scans scripts in a project, which likely involves reading and possibly executing or analyzing code files. Given the sibling tool 'analyze_script' exists separately, this may involve traversing the filesystem to locate scripts, which is at minimum a Read but could involve Execute-level operations.
From the tool's definition Tool name: 'scan_project_scripts' — implies scanning/executing or analyzing scripts within a project context. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs scan_project_scripts 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 scan_project_scripts, this is the rule to start with:
scan_project_scripts stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every scan_project_scripts call is checked against it from then on.
Questions about scan_project_scripts
scan_project_scripts is a execute tool on the Metis Public Health MCP server. It is categorised as a Execute tool in the Metis Public Health MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for scan_project_scripts: 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.
scan_project_scripts is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scan_project_scripts 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.
Set action: deny in the PolicyLayer policy for scan_project_scripts. 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.
scan_project_scripts 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.
More on Metis Public Health, and thousands of servers like it.
Across the catalogue