get_document_by_id

THE RISK

Low Risk

Why get_document_by_id needs a policy

This tool retrieves a single document from a search index without modifying, deleting, or executing any operations. It is a straightforward query operation with no side effects. The blast radius is minimal since it only returns existing data. Severity is low because unauthorized access to a single document poses limited risk compared to batch operations or data modification.

From the tool's definition Tool name is 'get_document_by_id' and description states 'Get a single document from an index by its internal Searchcraft ID (_id)'. The verb 'Get' and lack of any modification language indicate a retrieval operation.

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

POLICY

How to control get_document_by_id

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document_by_id": {}
  }
}

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

Create a free account and register Searchcraft MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Searchcraft MCP Server tools

Destructive delete_all_documents Delete all documents from an index. The index will continue to exist after all documents a Destructive delete_all_keys Delete all authentication keys on the Searchcraft cluster. Use with extreme caution! Destructive delete_all_stopwords Delete all custom stopwords from an index. This only affects custom stopwords, not the def Destructive delete_all_synonyms Delete all synonyms from an index. Destructive delete_document_by_id Delete a single document from an index by its internal Searchcraft ID (_id). Destructive delete_documents_by_field Delete one or several documents from an index by field term match (e.g., {id: Destructive delete_documents_by_query Delete one or several documents from an index by query match. Destructive delete_federation Delete a federation permanently.

All 48 Searchcraft MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_document_by_id

What does the get_document_by_id tool do? +

Get a single document from an index by its internal Searchcraft ID (_id). It is categorised as a Read tool in the Searchcraft MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_document_by_id? +

Register the Searchcraft MCP Server MCP server in PolicyLayer and add a rule for get_document_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 Searchcraft MCP Server. Nothing to install.

What risk level is get_document_by_id? +

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

Can I rate-limit get_document_by_id? +

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

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

get_document_by_id is provided by the Searchcraft MCP Server MCP server (searchcraft-inc/searchcraft-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Searchcraft MCP Server tool call.

Start from Searchcraft MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →