New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

metaharness_oia_audit

ADR-150 — composite weekly audit. Bundles oia-manifest + threat-model + mcp-scan into one timestamped record persisted to

SERVERClaude Flow SOURCEclaude-flow
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/metaharness-oia-audit.md

What metaharness_oia_audit does on Claude Flow

AI agents use metaharness_oia_audit to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.

Why metaharness_oia_audit is rated Medium

The tool aggregates security/audit artifacts (manifest, threat model, MCP scan) and persists a timestamped record, which is a Write operation — creating a new stored audit record. It does not appear to delete data or execute arbitrary code, but the truncated description reduces confidence slightly. Severity is medium because misuse could produce false or misleading audit records in an enterprise security context.

From the tool's definition 'composite weekly audit... Bundles oia-manifest + threat-model + mcp-scan into one timestamped record persisted to'

Questions about metaharness_oia_audit

What does the metaharness_oia_audit tool do? +

ADR-150 — composite weekly audit. Bundles oia-manifest + threat-model + mcp-scan into one timestamped record persisted to. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on metaharness_oia_audit? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for metaharness_oia_audit: 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.

What risk level is metaharness_oia_audit? +

metaharness_oia_audit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit metaharness_oia_audit? +

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

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

metaharness_oia_audit 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Flow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.