audit_sequences

What audit_sequences does on Mcpg

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

Why audit_sequences is rated Low

The tool name 'audit_sequences' most likely retrieves information about PostgreSQL sequences for auditing purposes—a read-only operation that queries database metadata. Without a description, confidence is moderate, but 'audit' strongly suggests passive inspection. If it performed destructive or write operations on sequences, the name would likely reflect that (e.g., 'reset_sequences', 'drop_sequences').

From the tool's definition Tool name 'audit_sequences' suggests inspection/querying of database sequence objects. The 'audit' prefix typically indicates monitoring, inspection, or review activity rather than modification or execution. No description provided.

The rule that runs audit_sequences safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "audit_sequences": {}
  }
}

Questions about audit_sequences