Returns a list of all submitters with their number of submitted programs.
AI agents call get_submitters to retrieve information from LODA API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries a list of submitters and their submission counts from the LODA/OEIS database. It performs no writes, deletions, code execution, or other modifications. It is a straightforward read-only query operation with minimal blast radius even if misused by an AI agent—the worst outcome would be redundant queries or information disclosure of already-public submitter statistics.
From the tool's definition Tool name 'get_submitters' with description 'Returns a list of all submitters with their number of submitted programs' indicates pure data retrieval with no side effects.
Attacks that exploit this kind of access
Returns a list of all submitters with their number of submitted programs. It is categorised as a Read tool in the LODA API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LODA API MCP Server MCP server in PolicyLayer and add a rule for get_submitters: 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 LODA API MCP Server. Nothing to install.
get_submitters 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_submitters 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_submitters. 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_submitters is provided by the LODA API MCP Server MCP server (loda-lang/loda-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 →