Low Risk

get_start_path

Recommend the best Tandem docs starting path for a desktop user, server admin, or developer.

Risk signalsAdmin/system-level operation

Part of the Docs Mcp server.

get_start_path is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DOCS MCP →

Free to start. No card required.

AI agents call get_start_path to retrieve information from Docs Mcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_start_path only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Docs Mcp policy for all 13 tools.

Get this rule live on your own Docs Mcp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DOCS MCP →

View all 13 tools →

These attack patterns abuse exactly the kind of access get_start_path gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_start_path only ever does what you allow.

SECURE DOCS MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_start_path tool do? +

Recommend the best Tandem docs starting path for a desktop user, server admin, or developer.. It is categorised as a Read tool in the Docs Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_start_path? +

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

What risk level is get_start_path? +

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

Can I rate-limit get_start_path? +

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

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

get_start_path is provided by the Docs MCP server (https://tandem.ac/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docs Mcp tool call.

Deterministic rules across all 13 Docs Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.