send_custom_request · Ssakone Pocketbase MCP: Risk & Policy

WHAT IT DOES

What send_custom_request does on Ssakone Pocketbase

AI agents invoke send_custom_request to trigger actions in Ssakone Pocketbase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why send_custom_request needs a policy

This tool sends arbitrary raw HTTP requests to the PocketBase API, meaning it can perform any operation — reads, writes, deletes, financial actions, or administrative changes — depending on the arguments provided.

From the tool's definition "Send raw HTTP requests to PocketBase API endpoints. Supports any authenticated user (admin or regular user) and maintains session state."

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_custom_request Rate-limited

send_custom_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_custom_request": {
      "limits": [
        {
          "counter": "send_custom_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ssakone Pocketbase, so you can run agents against it safely.

FAQ

Questions about send_custom_request

What does the send_custom_request tool do? +

Send raw HTTP requests to PocketBase API endpoints. Supports any authenticated user (admin or regular user) and maintains session state. It is categorised as a Execute tool in the Ssakone Pocketbase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_custom_request? +

Register the Ssakone Pocketbase MCP server in PolicyLayer and add a rule for send_custom_request: 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 Ssakone Pocketbase. Nothing to install.

What risk level is send_custom_request? +

send_custom_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_custom_request? +

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

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

send_custom_request is provided by the Ssakone Pocketbase MCP server (@iflow-mcp/ssakone-pocketbase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.