Validates ABACUS input parameters for common issues.
AI agents call validate_input to retrieve information from Abacus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs input validation—a query/check operation that examines parameters for correctness and returns validation results without side effects. No data is created, modified, deleted, or executed. It is purely informational, similar to a linter or validator. Severity is low because misuse would at worst accept invalid parameters or reject valid ones, with no blast radius beyond the validation scope itself.
From the tool's definition Tool name 'validate_input' and description 'Validates ABACUS input parameters for common issues' indicate a read-only validation operation that checks parameters without modifying data or executing calculations.
Documented attack patterns abuse exactly the kind of access validate_input gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Abacus, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_input:
{
"version": "1",
"default": "deny",
"tools": {
"validate_input": {}
}
}validate_input is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validates ABACUS input parameters for common issues. It is categorised as a Read tool in the Abacus MCP Server, which means it retrieves data without modifying state.
Register the Abacus MCP server in PolicyLayer and add a rule for validate_input: 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 Abacus. Nothing to install.
validate_input 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 validate_input 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 validate_input. 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.
validate_input is provided by the Abacus MCP server (phelanshao/abacus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Abacus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Abacus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.