Low Risk

get_snippet_by_id

Get a specific snippet by ID

How to control get_snippet_by_id ↓

AI agents call get_snippet_by_id to retrieve information from PhonePi MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves a single snippet by its identifier. It is a read-only operation with no destructive, write, execute, or financial capability. The blast radius of misuse is minimal—an attacker could only view stored snippet data, which may contain sensitive personal information but cannot be altered or deleted through this tool alone.

From the tool's definition Tool name and description indicate retrieval only: 'Get a specific snippet by ID' — a query operation that fetches data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_snippet_by_id gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PhonePi MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_snippet_by_id:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_snippet_by_id": {}
  }
}

get_snippet_by_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PhonePi MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_snippet_by_id tool do? +

Get a specific snippet by ID. It is categorised as a Read tool in the PhonePi MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_snippet_by_id? +

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

What risk level is get_snippet_by_id? +

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

Can I rate-limit get_snippet_by_id? +

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

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

get_snippet_by_id is provided by the PhonePi MCP server (priyankark/phonepi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PhonePi MCP tool call.

Deterministic rules across all 22 PhonePi MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

22 PhonePi MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.