AI agents use create_ml_project to create or update resources in SAS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SAS MCP Server environment.
The tool name contains 'create', which strongly implies a Write operation (creating a new resource). However, the description is empty, which significantly lowers confidence. In the context of a SAS Viya MCP server focused on executing SAS code and managing jobs/reports, creating an ML project likely involves creating a persistent project resource.
From the tool's definition Tool name 'create_ml_project' and empty description. The word 'create' suggests a Write operation that initializes a new ML project resource.
Documented attack patterns abuse exactly the kind of access create_ml_project 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 create_ml_project:
{
"version": "1",
"default": "deny",
"tools": {
"create_ml_project": {
"limits": [
{
"counter": "create_ml_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_ml_project 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.
create_ml_project. It is categorised as a Write tool in the SAS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SAS MCP Server MCP server in PolicyLayer and add a rule for create_ml_project: 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.
create_ml_project 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 create_ml_project 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 create_ml_project. 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.
create_ml_project 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.