AI agents call get_job_log to retrieve information from SAS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves execution logs from a completed job, which is a read-only operation that queries existing data without creating, modifying, deleting, or executing any code. The severity is low because log retrieval has minimal security impact—logs typically contain execution information rather than sensitive data that would pose high risk if accessed.
From the tool's definition Tool name 'get_job_log' and description 'Retrieve the log of a completed job' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_job_log 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 get_job_log:
{
"version": "1",
"default": "deny",
"tools": {
"get_job_log": {}
}
}get_job_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the log of a completed job. It is categorised as a Read tool in the SAS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAS MCP Server MCP server in PolicyLayer and add a rule for get_job_log: 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.
get_job_log 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 get_job_log 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 get_job_log. 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.
get_job_log 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.