Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to
AI agents use create_scout to create or update resources in Yutori MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yutori MCP environment.
This tool creates a new persistent monitoring scout, which is a data creation operation (Write category). The severity is medium because creating scouts could enable unintended surveillance or monitoring of arbitrary targets, though the operation itself is reversible (scouts can presumably be deleted via the sibling "delete_scout" tool).
From the tool's definition The tool name is "create_scout" and description states "Create a monitoring scout for continuous web monitoring." This is a creation operation that establishes a new monitoring entity.
Documented attack patterns abuse exactly the kind of access create_scout gives an agent:
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 create_scout:
{
"version": "1",
"default": "deny",
"tools": {
"create_scout": {
"limits": [
{
"counter": "create_scout_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_scout stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to. It is categorised as a Write tool in the Yutori MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yutori MCP server in PolicyLayer and add a rule for create_scout: 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.
create_scout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_scout 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.
Set action: deny in the PolicyLayer policy for create_scout. 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.
create_scout 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.
Start from Yutori MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Yutori MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.