Validate and store evidence files for assessments
AI agents use validate_evidence to create or update resources in NIST CSF 2 0 Assessment Platform — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NIST CSF 2 0 Assessment Platform environment.
The tool both validates and stores evidence files, which constitutes a write operation (creating/modifying stored data). The 'store' action creates new data persistently. Severity is medium since misuse could corrupt assessment evidence or introduce fraudulent supporting documentation, but it doesn't directly destroy data or move money.
From the tool's definition Validate and store evidence files for assessments
Documented attack patterns abuse exactly the kind of access validate_evidence gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NIST CSF 2 0 Assessment Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_evidence:
{
"version": "1",
"default": "deny",
"tools": {
"validate_evidence": {
"limits": [
{
"counter": "validate_evidence_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}validate_evidence stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validate and store evidence files for assessments. It is categorised as a Write tool in the NIST CSF 2 0 Assessment Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NIST CSF 2 0 Assessment Platform MCP server in PolicyLayer and add a rule for validate_evidence: 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 NIST CSF 2 0 Assessment Platform. Nothing to install.
validate_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the validate_evidence 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 validate_evidence. 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.
validate_evidence is provided by the NIST CSF 2 0 Assessment Platform MCP server (rocklambros/nist-csf-2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 49 NIST CSF 2 0 Assessment Platform tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
49 NIST CSF 2 0 Assessment Platform tools catalogued and risk-classified — across an index of 42,500+ MCP servers.