figma_get_images
AI agents call figma_get_images to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a clear indicator of a read-only query operation. Figma's API typically uses 'get' methods to fetch design assets and image data without modification. The absence of parameters like 'delete', 'create', or 'update' in the name, combined with similar read tools in the sibling list, confirms this as a Read operation.
From the tool's definition Tool name 'figma_get_images' indicates a retrieval operation ('get'). No description provided, but the naming pattern and context (alongside other read tools like 'airtable_get_record', 'amplitude_get_event_counts') strongly suggests data retrieval without…
Attacks that exploit this kind of access
figma_get_images. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for figma_get_images: 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 Integrations MCP. Nothing to install.
figma_get_images 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 figma_get_images 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 figma_get_images. 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.
figma_get_images is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →