Skip to main content
Glama
Desmond-Labs

Supabase Storage MCP

by Desmond-Labs

get_security_status

Check current security configuration and audit details for Supabase Storage to verify access controls and compliance status.

Instructions

Get current security configuration and audit information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function that executes the get_security_status tool logic. It retrieves audit log, rate limit info, and security config to construct the response.
    async function handleSecurityStatus() {
      const auditLog = getAuditLog();
      const securityStatus: SecurityStatusResponse = {
        security_config: SECURITY_CONFIG,
        rate_limit_status: {
          active_limits: getRateLimitStoreSize(),
          current_window: SECURITY_CONFIG.RATE_LIMIT_WINDOW
        },
        audit_log: {
          total_entries: auditLog.length,
          recent_entries: auditLog.slice(-10).map(entry => ({
            timestamp: new Date(entry.timestamp).toISOString(),
            tool: entry.toolName,
            success: entry.success,
            error: entry.error || 'none'
          }))
        },
        server_info: {
          name: 'supabase-storage-mcp',
          version: '1.0.0',
          uptime: process.uptime(),
          node_version: process.version
        }
      };
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(securityStatus, null, 2)
          }
        ]
      };
    }
  • Tool schema definition including input schema (empty object) and description, registered in ListTools handler.
      name: 'get_security_status',
      description: 'Get current security configuration and audit information',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      }
    },
  • src/index.ts:479-480 (registration)
    Registration of the tool handler in the main CallToolRequestSchema switch statement.
    case 'get_security_status':
      return await handleSecurityStatus();
  • SECURITY_CONFIG constant used by the handler to provide configuration details in the response.
    export const SECURITY_CONFIG: SecurityConfig = {
      ENABLE_RATE_LIMITING: true,
      ENABLE_THREAT_DETECTION: true,
      ENABLE_AUDIT_LOGGING: true,
      ENABLE_INPUT_VALIDATION: true,
      ENABLE_FILE_SECURITY: true,
      
      // Rate limiting configuration
      RATE_LIMIT_WINDOW: 60000, // 1 minute
      MAX_REQUESTS_PER_WINDOW: 100,
      GLOBAL_RATE_LIMIT: 1000,
      IP_RATE_LIMIT: 200,
      USER_RATE_LIMIT: 500,
      
      // File security limits
      MAX_FILE_SIZE: 50 * 1024 * 1024, // 50MB
      MAX_BATCH_SIZE: 500,
      ALLOWED_MIME_TYPES: [
        'image/jpeg', 'image/jpg', 'image/png', 'image/webp', 
        'image/gif', 'image/svg+xml', 'image/bmp', 'image/tiff',
        'application/zip', 'application/x-zip-compressed'
      ],
      
      // Security thresholds
      MAX_PROMPT_LENGTH: 10000,
      SUSPICIOUS_ACTIVITY_THRESHOLD: 5,
      HIGH_RISK_SCORE_THRESHOLD: 80,
      
      // Session and authentication
      SESSION_TIMEOUT: 3600, // 1 hour
      JWT_EXPIRY: 7200 // 2 hours
    };
  • Helper function getAuditLog() called by the handler to retrieve recent audit log entries.
    export function getAuditLog(): AuditEntry[] {
      return [...auditLog]; // Return copy to prevent external modification
    }
  • Helper function getRateLimitStoreSize() called by the handler to get active rate limits count.
    export function getRateLimitStoreSize(): number {
      return rateLimitStore.size;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify permissions needed, rate limits, or what the output includes (e.g., format, scope). This leaves significant gaps for a security-related tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the key information ('Get current security configuration and audit information') with zero wasted words. It's appropriately sized for a no-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'security configuration and audit information' entails or how it's returned, which is important for an agent to use it effectively. With no annotations, it should provide more behavioral context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description doesn't need to compensate for any parameter documentation gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('current security configuration and audit information'), making it easy to understand what it does. However, it doesn't differentiate itself from sibling tools, which are all file/bucket operations, so it's not a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the purpose alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Desmond-Labs/supabase-storage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server