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

vibecontrols_audit_export

Export audit logs in a specified format.

SERVERVibecontrols SOURCE@vibecontrols/mcp
Medium RISK CLASS
Category Write
Parameters 40 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-audit-export.md

What vibecontrols_audit_export does on Vibecontrols

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

ParameterTypeRequiredDescription
action string — Filter by action type
format string — Export format: json or csv
status string — Filter by status
resourceType string — Filter by resource type

Parameters from the server's own tool schema.

Why vibecontrols_audit_export is rated Medium

An AI agent can call vibecontrols_audit_export faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.

Questions about vibecontrols_audit_export

What does the vibecontrols_audit_export tool do? +

Export audit logs in a specified format. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vibecontrols_audit_export accept? +

vibecontrols_audit_export accepts 4 parameters: action, format, status, resourceType. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_audit_export? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_audit_export: 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 Vibecontrols. Nothing to install.

What risk level is vibecontrols_audit_export? +

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

Can I rate-limit vibecontrols_audit_export? +

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

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

vibecontrols_audit_export is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Vibecontrols, 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 Vibecontrols'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.