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

audit_security

A read tool on the Supabase MCP Server - Self-Hosted Edition MCP server.

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/audit-security.md

What audit_security does on Supabase MCP Server - Self-Hosted Edition

AI agents call audit_security to retrieve information from Supabase MCP Server - Self-Hosted Edition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why audit_security is rated Low

The name 'audit_security' most plausibly refers to a read-only security audit or review operation that checks RLS policies, permissions, and configurations without modifying them. This aligns with sibling tools like 'analyze_rls_coverage' and 'analyze_performance' which appear to be read/analysis tools. However, the empty description significantly lowers confidence.

From the tool's definition Tool name: 'audit_security'; description is empty and uninformative.

Questions about audit_security

What does the audit_security tool do? +

audit_security is a read tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Read tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on audit_security? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for audit_security: 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 Supabase MCP Server - Self-Hosted Edition. Nothing to install.

What risk level is audit_security? +

audit_security is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit audit_security? +

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

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

audit_security is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Supabase MCP Server - Self-Hosted Edition, 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 Supabase MCP Server - Self-Hosted Edition'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.