AI agents call get_spec_history to retrieve information from Scrumdo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve or query specification history from ScrumDo boards without modifying state. The 'get_' prefix is a standard convention for read operations. While the empty description reduces confidence slightly, the naming pattern and context (ScrumDo board operations) strongly suggest this is a data retrieval function with no side effects.
From the tool's definition Tool name 'get_spec_history' indicates retrieval of historical specification data. No description provided, but the 'get_' prefix and historical context operation suggest query/read semantics consistent with sibling tools like 'add_comment' and 'assign_card'…
Attacks that exploit this kind of access
get_spec_history. It is categorised as a Read tool in the Scrumdo MCP Server, which means it retrieves data without modifying state.
Register the Scrumdo MCP server in PolicyLayer and add a rule for get_spec_history: 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 Scrumdo. Nothing to install.
get_spec_history 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_spec_history 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_spec_history. 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_spec_history is provided by the Scrumdo MCP server (scrumdollc/scrumdo-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 →