Get agent strategy details including required parameters (instruction, query, model, tools, etc.) for agent_parameters config.
AI agents call get_agent_strategy to retrieve information from Pulse Workflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing agent strategy configuration and parameters. It has no side effects, does not create, modify, delete, or execute operations. It is purely informational/read-only access to workflow configuration metadata.
From the tool's definition Tool name is 'get_agent_strategy' and description states 'Get agent strategy details' — uses 'Get' verb indicating retrieval of existing configuration data without modification.
Attacks that exploit this kind of access
Get agent strategy details including required parameters (instruction, query, model, tools, etc.) for agent_parameters config. It is categorised as a Read tool in the Pulse Workflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for get_agent_strategy: 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 Pulse Workflow MCP Server. Nothing to install.
get_agent_strategy 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_agent_strategy 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_agent_strategy. 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_agent_strategy is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-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 →