waypath_session_start

Server Waypath thestack-ai/waypath

Category Execute

Risk class High

Parameters 00 required

WHAT IT DOES

What waypath_session_start does on Waypath

AI agents invoke waypath_session_start to trigger actions in Waypath. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why waypath_session_start needs a policy

waypath_session_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

waypath_session_start Rate-limited

waypath_session_start stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "waypath_session_start": {
      "limits": [
        {
          "counter": "waypath_session_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Waypath, so you can run agents against it safely.

FAQ

Questions about waypath_session_start

What does the waypath_session_start tool do? +

Read-only context pack builder for the beginning of a coding or planning session. Assembles a prioritized brief from recent decisions, active preferences, seed entities, and related graph context. Does not write to the database. Call once per session before substantive work; for mid-session lookups use waypath_recall or waypath_graph_query instead. All parameters are optional — pass what is known; omitted fields fall back to project defaults. It is categorised as a Execute tool in the Waypath MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on waypath_session_start? +

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

What risk level is waypath_session_start? +

waypath_session_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit waypath_session_start? +

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

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

waypath_session_start is provided by the Waypath MCP server (thestack-ai/waypath). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.