get_report_image

THE RISK

Low Risk

Why get_report_image needs a policy

This tool retrieves and renders a pre-existing report section as an image file. It performs no write, delete, code execution, or financial operations. The action is a query/retrieval that produces a read-only visual representation of data. No side effects or irreversible changes occur.

From the tool's definition Tool name 'get_report_image' and description 'Render a Visual Analytics report section as an image' indicate retrieval and rendering of existing report data.

Documented attack patterns abuse exactly the kind of access get_report_image gives an agent:

POLICY

How to control get_report_image

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_report_image:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_report_image": {}
  }
}

get_report_image is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register SAS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SAS MCP Server tools

Destructive cancel_job Cancel a running job. Execute execute_sas_code execute_sas_code Execute run_ml_project Run an AutoML pipeline automation project. Execute score_data Score data against a published model or decision (MAS module). Execute submit_batch_job Submit a SAS job for asynchronous execution via the Job Execution service. Write create_ml_project create_ml_project Write promote_table_to_memory promote_table_to_memory Write upload_data Upload CSV data into a CAS table.

All 27 SAS MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_report_image

What does the get_report_image tool do? +

Render a Visual Analytics report section as an image. It is categorised as a Read tool in the SAS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_report_image? +

Register the SAS MCP Server MCP server in PolicyLayer and add a rule for get_report_image: 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.

What risk level is get_report_image? +

get_report_image is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_report_image? +

Yes. Add a rate_limit block to the get_report_image 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.

How do I block get_report_image completely? +

Set action: deny in the PolicyLayer policy for get_report_image. 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.

What MCP server provides get_report_image? +

get_report_image 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.

Enforce policy on every SAS MCP Server tool call.

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.

CHECK YOUR STACK →