get_visualization
Fetch a chart artifact generated by a council session or LOCUS determination. Returns the machine-readable spec (the data behind the chart) plus the stable SVG URL, or the raw SVG itself with include_svg=true. Artifact ids appear in session results as 'visualizations' / 'visualization' reference ...
This record as markdown: /tools/com-meta-council-decision-intelligence/get-visualization.md
What get_visualization does on Meta Council
AI agents call get_visualization to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
artifact_id | string | Yes | 32-hex artifact id from a visualization reference |
include_svg | boolean | — | Also return the full SVG markup (default false) |
Parameters from the server's own tool schema.
Why get_visualization is rated Low
This tool retrieves pre-generated visualization artifacts and their underlying data. It performs a query operation that has no side effects—it does not create, modify, delete, or execute anything. The presence of authentication and tenant boundaries is standard security practice for read operations and does not elevate the category. No financial, destructive, or code-execution capability is present.
From the tool's definition The tool description explicitly states it 'Fetch[es] a chart artifact' and 'Returns the machine-readable spec (the data behind the chart) plus the stable SVG URL'.
Attacks that exploit this kind of access
The rule that runs get_visualization safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_visualization, this is the rule to start with:
get_visualization is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every get_visualization call is checked against it from then on.
Questions about get_visualization
Fetch a chart artifact generated by a council session or LOCUS determination. Returns the machine-readable spec (the data behind the chart) plus the stable SVG URL, or the raw SVG itself with include_svg=true. Artifact ids appear in session results as 'visualizations' / 'visualization' reference blocks. Requires authentication and enforces the artifact owner's tenant boundary. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_visualization accepts 2 parameters: artifact_id, include_svg. Required: artifact_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for get_visualization: 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 Council. Nothing to install.
get_visualization 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_visualization 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_visualization. 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_visualization is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue