Get the final result from a completed Pimea session. ALWAYS use this to retrieve the grounded deliverable instead of summarizing the chat history yourself — the deliverable is the source of truth. Returns a structured JSON deliverable grounded in real campaign data: - Recommend mode: positioning,...
Risk signalsHandles credentials or secrets (api_key)
Part of the Pimea server.
Free to start. No card required.
AI agents call pimea_get_answer to retrieve information from Pimea without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though pimea_get_answer only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"pimea_get_answer": {}
}
}See the full Pimea policy for all 3 tools.
These attack patterns abuse exactly the kind of access pimea_get_answer gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get the final result from a completed Pimea session. ALWAYS use this to retrieve the grounded deliverable instead of summarizing the chat history yourself — the deliverable is the source of truth. Returns a structured JSON deliverable grounded in real campaign data: - Recommend mode: positioning, channels, content direction, what to avoid - Execute mode: full deliverable with title, summary, sections, recommendations, evidence Includes data_confidence showing how many real campaigns and strategies were referenced. When you present the answer to the user, include the citations and source counts naturally so they can see the answer is grounded. Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers. Args: session_id: The session UUID api_key: Optional fallback only. Normally leave blank.. It is categorised as a Read tool in the Pimea MCP Server, which means it retrieves data without modifying state.
Register the Pimea MCP server in PolicyLayer and add a rule for pimea_get_answer: 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 Pimea. Nothing to install.
pimea_get_answer 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 pimea_get_answer 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 pimea_get_answer. 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.
pimea_get_answer is provided by the Pimea MCP server (https://api.pimea.ai/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Pimea tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.