AI agents call get_monitor_deep_analysis to retrieve information from Pipiads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
task_id | string | Yes | Monitor task ID |
dimension | number | Yes | Analysis dimension |
Parameters from the server's own tool schema.
This tool retrieves or queries existing campaign analysis information with no side effects. It fits the Read category: no data is created, modified, deleted, or irreversibly changed. The analysis is presumably already computed, and the tool simply fetches it. Severity is low because read operations have minimal blast radius unless the data itself is highly sensitive (which is not indicated here).
From the tool's definition Tool name 'get_monitor_deep_analysis' and description 'Get deep campaign analysis for a monitor task' indicate retrieval of pre-computed analysis data. The verb 'get' and passive 'analysis' phrasing show no data modification, deletion, or command execution.
Attacks that exploit this kind of access
Get deep campaign analysis for a monitor task. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_monitor_deep_analysis accepts 2 parameters: task_id, dimension. Required: task_id, dimension. The full parameter table on this page comes from the server's own tool schema.
Register the Pipiads MCP server in PolicyLayer and add a rule for get_monitor_deep_analysis: 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 Pipiads. Nothing to install.
get_monitor_deep_analysis 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_monitor_deep_analysis 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_monitor_deep_analysis. 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_monitor_deep_analysis is provided by the Pipiads MCP server (pipiads-mcp-server). 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 →