Get technology switch signals (companies changing tools) and career moves (people changing jobs). Shows buying intent and market movement.
AI agents call get_signals to retrieve information from AgentData MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation that fetches structured business intelligence data. It does not create, modify, delete, or execute any code. The tool only reads and returns existing signals about technology changes and job transitions. The blast radius of misuse is limited to potential privacy concerns around personnel data exposure, but the operation itself is non-destructive and non-invasive.
From the tool's definition Tool retrieves technology switch signals and career move data from the company intelligence platform. Described as showing 'buying intent and market movement' — passive data retrieval with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
Get technology switch signals (companies changing tools) and career moves (people changing jobs). Shows buying intent and market movement. It is categorised as a Read tool in the AgentData MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AgentData MCP Server MCP server in PolicyLayer and add a rule for get_signals: 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 AgentData MCP Server. Nothing to install.
get_signals 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_signals 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_signals. 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_signals is provided by the AgentData MCP Server MCP server (nick-timms/agentdata-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 →