search_submissions_by_date
AI agents call search_submissions_by_date to retrieve information from JotForm API Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool searches or queries form submissions filtered by date criteria. This is a read-only operation that retrieves data without modifying, deleting, or executing external operations. The empty description lowers confidence slightly, but the name and context from the server description clearly indicate data retrieval functionality typical of Read category tools.
From the tool's definition Tool name 'search_submissions_by_date' and server description stating 'advanced submission search by date ranges' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
search_submissions_by_date. It is categorised as a Read tool in the JotForm API Server MCP Server, which means it retrieves data without modifying state.
Register the JotForm API Server MCP server in PolicyLayer and add a rule for search_submissions_by_date: 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 JotForm API Server. Nothing to install.
search_submissions_by_date 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 search_submissions_by_date 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 search_submissions_by_date. 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.
search_submissions_by_date is provided by the JotForm API Server MCP server (the-ai-workshops/jotform-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 →