csp_evaluate
Evaluate a Content-Security-Policy string the way CSP Evaluator does, before you ship it: parses directives, catches typos, unquoted keywords and deprecated directives, then checks script execution (unsafe-inline without nonce/hash, unsafe-eval, wildcards, http:/https:/data: sources, 40+ known al...
This record as markdown: /tools/com-it-scorptech-x402/csp-evaluate.md
What csp_evaluate does on ScorpTech x402 API
AI agents call csp_evaluate to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
meta | boolean | — | Policy is delivered in a <meta> tag (frame-ancestors, report-uri and sandbox are then ignored by browsers) |
policy | string | Yes | The policy value (without the header name) |
reportOnly | boolean | — | Policy is sent as Content-Security-Policy-Report-Only |
Parameters from the server's own tool schema.
Why csp_evaluate is rated Low
Even though csp_evaluate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs csp_evaluate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For csp_evaluate, this is the rule to start with:
csp_evaluate 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 ScorpTech x402 API, apply this rule, and every csp_evaluate call is checked against it from then on.
Questions about csp_evaluate
Evaluate a Content-Security-Policy string the way CSP Evaluator does, before you ship it: parses directives, catches typos, unquoted keywords and deprecated directives, then checks script execution (unsafe-inline without nonce/hash, unsafe-eval, wildcards, http:/https:/data: sources, 40+ known allowlist-bypass hosts with JSONP / AngularJS / user content), object-src, base-uri, frame-ancestors, form-action, reporting and Trusted Types. Returns findings with severity and fixes, a 0-100 score and A-F grade, and a strict nonce-based policy template. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/csp-evaluate. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
csp_evaluate accepts 3 parameters: meta, policy, reportOnly. Required: policy. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for csp_evaluate: 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 ScorpTech x402 API. Nothing to install.
csp_evaluate 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 csp_evaluate 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 csp_evaluate. 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.
csp_evaluate is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue