wake.read

Read project-scoped session orientation: selected identity and continuity summaries plus links to deeper source routes. This is not a complete export.

SERVERAgenttool SOURCEhttps://api.agenttool.dev/v1/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-agenttool-agenttool/wake.read.md

WHAT IT DOES

What wake.read does on Agenttool

AI agents call wake.read to retrieve information from Agenttool without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why wake.read is rated Low

Even though wake.read only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wake.read safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agenttool, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wake.read, this is the rule to start with:

wake.read Allowed

wake.read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wake.read": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenttool, apply this rule, and every wake.read call is checked against it from then on.

FAQ

Questions about wake.read

What does the wake.read tool do? +

Read project-scoped session orientation: selected identity and continuity summaries plus links to deeper source routes. This is not a complete export. It is categorised as a Read tool in the Agenttool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wake.read? +

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

What risk level is wake.read? +

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

Can I rate-limit wake.read? +

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

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

wake.read is provided by the Agenttool MCP server (https://api.agenttool.dev/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agenttool, and thousands of servers like it.

This server

All 84 Agenttool tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →