Generate a client-side session ID for your own bookkeeping. SidClaw does
AI agents call sidclaw_session_start as a supporting operation in Sdk workflows.
This tool only generates a local session identifier for client-side tracking purposes. It does not read external data, write to any system, execute code, delete anything, or involve financial operations. It is a utility function for generating an ID used in bookkeeping/tracking. The description appears truncated ('SidClaw does'), slightly lowering confidence, but the primary action described is benign ID generation.
From the tool's definition Generate a client-side session ID for your own bookkeeping
Documented attack patterns abuse exactly the kind of access sidclaw_session_start gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sdk, and nothing reaches the server without passing your rules. This is the rule we recommend for sidclaw_session_start:
{
"version": "1",
"default": "deny",
"tools": {
"sidclaw_session_start": {
"limits": [
{
"counter": "sidclaw_session_start_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} sidclaw_session_start gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a client-side session ID for your own bookkeeping. SidClaw does. It is categorised as a Other tool in the Sdk MCP Server, which means it performs auxiliary operations.
Register the Sdk MCP server in PolicyLayer and add a rule for sidclaw_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 Sdk. Nothing to install.
sidclaw_session_start is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sidclaw_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.
Set action: deny in the PolicyLayer policy for sidclaw_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.
sidclaw_session_start is provided by the Sdk MCP server (@sidclaw/sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sdk, 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.
10 Sdk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.