request_verification

// WHEN AI AGENTS USE THIS TOOL

AI agents use request_verification to create or modify resources in PocketBase MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON REQUEST_VERIFICATION

Without a policy, an AI agent could call request_verification repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach PocketBase MCP Server.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

imatrixme-pocketbase-mcp-server.yaml

tools:
  request_verification:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full PocketBase MCP Server policy for all 24 tools.

// DETAILS

Tool Name request_verification

Category Write

MCP Server PocketBase MCP Server MCP Server

Risk Level Medium

// MORE POCKETBASE MCP SERVER TOOLS

Destructive confirm_password_reset Destructive delete_record Destructive request_password_reset Write auth_refresh Write authenticate_user Write authenticate_with_oauth2 Write authenticate_with_otp Write backup_database

View all 24 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like request_verification have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Firecrawl Web Scraping Server firecrawl_generate_llmstxt AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update

// RELATED READING

// FAQ

What does the request_verification tool do? +

Request email verification. It is categorised as a Write tool in the PocketBase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on request_verification? +

Add a rule in your Intercept YAML policy under the tools section for request_verification. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the PocketBase MCP Server MCP server.

What risk level is request_verification? +

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

Can I rate-limit request_verification? +

Yes. Add a rate_limit block to the request_verification rule in your Intercept 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 request_verification completely? +

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

request_verification is provided by the PocketBase MCP Server MCP server (imatrixme/pocketbase-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.