metaharness_mcp_scan

ADR-150 — static security scan of

SERVERHamza Agent Hub 252 SOURCEhamzachallenge3-dev/hamza-agent-hub-252

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/hamza-agent-hub-252/metaharness-mcp-scan.md

WHAT IT DOES

What metaharness_mcp_scan does on Hamza Agent Hub 252

AI agents call metaharness_mcp_scan to retrieve information from Hamza Agent Hub 252 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why metaharness_mcp_scan is rated Low

Static security scanning retrieves and analyzes code/configuration without modifying or executing it. The incomplete description ('static security scan of') limits confidence slightly, but the operation is clearly a read-type analysis tool. No destructive, financial, or execution capabilities are indicated.

From the tool's definition Tool name contains 'scan' and description references 'static security scan', which are read-only inspection operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs metaharness_mcp_scan safely

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

metaharness_mcp_scan Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every metaharness_mcp_scan call is checked against it from then on.

FAQ

Questions about metaharness_mcp_scan

What does the metaharness_mcp_scan tool do? +

ADR-150 — static security scan of. It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on metaharness_mcp_scan? +

Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for metaharness_mcp_scan: 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 Hamza Agent Hub 252. Nothing to install.

What risk level is metaharness_mcp_scan? +

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

Can I rate-limit metaharness_mcp_scan? +

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

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

metaharness_mcp_scan is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hamza Agent Hub 252, and thousands of servers like it.

This server

All 581 Hamza Agent Hub 252 tools →

Across the catalogue

The MCP Attack Database →

Guides

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