Get number of form submissions received this month.
AI agents call get_usage 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.
This tool retrieves usage statistics (submission count) for the current month. It performs a read-only query operation with no capability to modify, delete, or execute external actions. The data returned is non-sensitive aggregate information. The blast radius of misuse is minimal — an attacker gaining access could only observe form submission statistics, which provides limited actionable intelligence.
From the tool's definition Tool name is 'get_usage' and description states 'Get number of form submissions received this month' — purely retrieves/queries aggregated submission count data without modification or side effects.
Attacks that exploit this kind of access
Get number of form submissions received this month. 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 get_usage: 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.
get_usage 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_usage 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_usage. 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_usage 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 →