sxo_score
Score any content against SXO criteria. Returns: BLUF compliance, Table Trap, Information Gain, heading architecture, readability, keyword density. Example: sxo_score({ content:
This record as markdown: /tools/io-github-0nork-0nmcp/sxo-score.md
What sxo_score does on 0nmcp
AI agents call sxo_score to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sxo_score is rated Low
This tool retrieves and analyzes content to produce scoring metrics (compliance, readability, keyword density, etc.). It is a read-only analytical operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius is minimal—misuse would only produce inaccurate scores, not harm systems or data.
From the tool's definition Tool name 'sxo_score' and description 'Score any content against SXO criteria' with return values 'BLUF compliance, Table Trap, Information Gain, heading architecture, readability, keyword density' indicate a purely analytical/evaluation function that…
Attacks that exploit this kind of access
The rule that runs sxo_score safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sxo_score, this is the rule to start with:
sxo_score 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 0nmcp, apply this rule, and every sxo_score call is checked against it from then on.
Questions about sxo_score
Score any content against SXO criteria. Returns: BLUF compliance, Table Trap, Information Gain, heading architecture, readability, keyword density. Example: sxo_score({ content:. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for sxo_score: 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 0nmcp. Nothing to install.
sxo_score 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 sxo_score 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 sxo_score. 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.
sxo_score is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue