verify_jwt_secret
A read tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/verify-jwt-secret.md
What verify_jwt_secret does on Supabase MCP Server - Self-Hosted Edition
AI agents call verify_jwt_secret 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 verify_jwt_secret is rated Low
Verification operations are generally read-only—they inspect or validate data without side effects. However, confidence is moderate (0.72) because the empty description prevents confirmation of whether this tool might also perform writes, executions, or other operations. The 'verify' semantic and Supabase's auth-focused context suggest a read-like operation, but the lack of detail introduces uncertainty.
From the tool's definition Tool name 'verify_jwt_secret' indicates verification of a JWT secret, which is a read operation checking validity or correctness of a credential. The description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs verify_jwt_secret safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_jwt_secret, this is the rule to start with:
verify_jwt_secret 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 Supabase MCP Server - Self-Hosted Edition, apply this rule, and every verify_jwt_secret call is checked against it from then on.
Questions about verify_jwt_secret
verify_jwt_secret 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.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for verify_jwt_secret: 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.
verify_jwt_secret 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 verify_jwt_secret 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 verify_jwt_secret. 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.
verify_jwt_secret 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