metaharness_threat_model
ADR-150 — enterprise-grade threat model from
This record as markdown: /tools/io-github-ruvnet-claude-flow/metaharness-threat-model.md
What metaharness_threat_model does on Claude Flow
AI agents call metaharness_threat_model to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why metaharness_threat_model is rated Low
The tool appears designed to query or retrieve threat model information (a read operation) for enterprise security analysis. The name does not indicate execution of threats, modification of systems, or destructive capabilities. Without seeing the full description (it is truncated at 'from'), confidence is moderate but the semantic suggests a read/query pattern typical of threat modeling consultation tools.
From the tool's definition Tool name 'threat_model' combined with prefix 'metaharness_' and reference to 'ADR-150 — enterprise-grade threat model' suggests retrieval or analysis of existing threat model data rather than modification or execution of operations.
Attacks that exploit this kind of access
The rule that runs metaharness_threat_model safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For metaharness_threat_model, this is the rule to start with:
metaharness_threat_model is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every metaharness_threat_model call is checked against it from then on.
Questions about metaharness_threat_model
ADR-150 — enterprise-grade threat model from. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for metaharness_threat_model: 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 Claude Flow. Nothing to install.
metaharness_threat_model is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the metaharness_threat_model 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 metaharness_threat_model. 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.
metaharness_threat_model is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue