metaharness_audit_list
ADR-150 iter 16 — list timestamped records from the
This record as markdown: /tools/ruflo/metaharness-audit-list.md
What metaharness_audit_list does on Ruflo
AI agents call metaharness_audit_list to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why metaharness_audit_list is rated Low
This tool lists audit records, which is a read-only operation that retrieves data without side effects. The description is incomplete ('from the' is cut off), but the verb 'list' and context of audit records strongly suggest passive data retrieval.
From the tool's definition Tool name 'metaharness_audit_list' and description fragment 'list timestamped records from the' indicate a query/retrieval operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs metaharness_audit_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For metaharness_audit_list, this is the rule to start with:
metaharness_audit_list 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 Ruflo, apply this rule, and every metaharness_audit_list call is checked against it from then on.
Questions about metaharness_audit_list
ADR-150 iter 16 — list timestamped records from the. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for metaharness_audit_list: 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 Ruflo. Nothing to install.
metaharness_audit_list 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_audit_list 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_audit_list. 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_audit_list is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue