List active policy rules for the current tenant (or a specific agent).
AI agents call sidclaw_policies to retrieve information from Sdk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data (policy rules) for the current tenant or agent. It has no destructive, write, execute, or financial implications. Misuse would at worst expose policy metadata to an unauthorized user, but the blast radius is minimal since policies themselves are defensive controls. The confidentiality risk is low if access controls on the governance proxy are properly enforced.
From the tool's definition Tool name 'sidclaw_policies' and description 'List active policy rules' — purely retrieves/queries data with no side effects. The verb 'list' indicates a read-only operation.
Documented attack patterns abuse exactly the kind of access sidclaw_policies 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_policies:
{
"version": "1",
"default": "deny",
"tools": {
"sidclaw_policies": {}
}
}sidclaw_policies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List active policy rules for the current tenant (or a specific agent). It is categorised as a Read tool in the Sdk MCP Server, which means it retrieves data without modifying state.
Register the Sdk MCP server in PolicyLayer and add a rule for sidclaw_policies: 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_policies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sidclaw_policies 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_policies. 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_policies 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.