get_session_compliance

Score an OpenClaw session against its security policy.

SERVERNodebench SOURCEnodebench-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/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.

Questions about get_session_compliance

What does the get_session_compliance tool do? +

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.

How do I enforce a policy on get_session_compliance? +

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.

What risk level is get_session_compliance? +

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

Can I rate-limit get_session_compliance? +

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.

How do I block get_session_compliance completely? +

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.

What MCP server provides get_session_compliance? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.