get_scout_detail

THE RISK

Low Risk

Why get_scout_detail needs a policy

This tool retrieves information about an existing scout without creating, modifying, deleting, or executing any operations. It is a straightforward query/fetch operation that presents no risk of data loss, code execution, or unintended side effects.

From the tool's definition Tool name 'get_scout_detail' and description 'Get detailed information about a specific scout' indicate a retrieval operation with no modification or side effects.

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

POLICY

How to control get_scout_detail

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

policy.json

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

get_scout_detail 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 Yutori MCP — 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 Yutori MCP tools

Destructive delete_scout Permanently delete a scout and all its data. This action cannot be undone. Execute run_browsing_task Execute a one-time web browsing task. The navigator agent runs a browser and Execute run_research_task Execute a one-time deep web research task. The research agent searches, Write create_scout Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to Write edit_scout Update an existing scout Read get_browsing_task_result Poll for browsing task status and result. Call until status is Read get_research_task_result Poll for research task status and result. Call until status is Read get_scout_updates Get paginated updates/reports for a scout. Each update contains findings from a run.

All 11 Yutori MCP 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_scout_detail

What does the get_scout_detail tool do? +

Get detailed information about a specific scout. It is categorised as a Read tool in the Yutori MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_scout_detail? +

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

What risk level is get_scout_detail? +

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

Can I rate-limit get_scout_detail? +

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

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

get_scout_detail is provided by the Yutori MCP server (yutori-ai/yutori-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yutori MCP tool call.

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

CHECK YOUR STACK →