get_session_compliance
Score an OpenClaw session against its security policy.
This record as markdown: /tools/io-github-homenshum-nodebench/get-session-compliance.md
What get_session_compliance does on Nodebench
AI agents call get_session_compliance to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_session_compliance is rated Low
This tool retrieves and evaluates compliance metrics for an existing session. It performs analysis and scoring against a pre-defined security policy, which is a read-only assessment with no side effects, data modification, execution, or financial impact. The low severity reflects that misuse would only expose compliance information rather than cause damage or unauthorized state changes.
From the tool's definition Tool name 'get_session_compliance' and description 'Score an OpenClaw session against its security policy' indicate a query/assessment operation.
Attacks that exploit this kind of access
The rule that runs get_session_compliance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_session_compliance, this is the rule to start with:
get_session_compliance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every get_session_compliance call is checked against it from then on.
Questions about get_session_compliance
Score an OpenClaw session against its security policy. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for get_session_compliance: 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 Nodebench. Nothing to install.
get_session_compliance 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 get_session_compliance 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 get_session_compliance. 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.
get_session_compliance is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue