Score data against a published model or decision (MAS module).
AI agents invoke score_data to trigger actions in SAS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Scoring data against a published model or decision triggers an external computation/inference operation on a MAS (Micro Analytic Score) module. This is an execution of a deployed analytical process whose effects depend on the input arguments and model, placing it firmly in the Execute category.
From the tool's definition Score data against a published model or decision (MAS module)
Documented attack patterns abuse exactly the kind of access score_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for score_data:
{
"version": "1",
"default": "deny",
"tools": {
"score_data": {
"limits": [
{
"counter": "score_data_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}score_data stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Score data against a published model or decision (MAS module). It is categorised as a Execute tool in the SAS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SAS MCP Server MCP server in PolicyLayer and add a rule for score_data: 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 SAS MCP Server. Nothing to install.
score_data is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the score_data 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 score_data. 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.
score_data is provided by the SAS MCP Server MCP server (sassoftware/sas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 SAS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.