Get, download, and save a Meta ad image locally, returning the file path. Args: ad_id: Meta Ads ad ID access_token: Meta API access token (optional - will use cached token if not provided) output_dir: Directory to save the image file (default: 'ad_images') Returns: The file path to the saved imag...
AI agents use save_ad_image_locally to create or update resources in Meta Ads MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Ads MCP environment.
This tool fetches a remote image and writes it to the local disk. It has a persistent side effect (file creation) but is reversible (file can be deleted). It doesn't execute code or destroy data, so Write is the most appropriate category. Severity is medium because it writes arbitrary files to a user-specified directory, which could be misused for path traversal or disk exhaustion.
From the tool's definition 'download, and save a Meta ad image locally, returning the file path' — writes a file to the local filesystem
Documented attack patterns abuse exactly the kind of access save_ad_image_locally gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta Ads MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for save_ad_image_locally:
{
"version": "1",
"default": "deny",
"tools": {
"save_ad_image_locally": {
"limits": [
{
"counter": "save_ad_image_locally_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_ad_image_locally 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.
Get, download, and save a Meta ad image locally, returning the file path. Args: ad_id: Meta Ads ad ID access_token: Meta API access token (optional - will use cached token if not provided) output_dir: Directory to save the image file (default: 'ad_images') Returns: The file path to the saved image, or an error message string. It is categorised as a Write tool in the Meta Ads MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta Ads MCP server in PolicyLayer and add a rule for save_ad_image_locally: 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 Meta Ads MCP. Nothing to install.
save_ad_image_locally 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 save_ad_image_locally 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 save_ad_image_locally. 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.
save_ad_image_locally is provided by the Meta Ads MCP server (pipeboard-co/meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Meta Ads MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Meta Ads MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.