speechwire_list_judge_types
AI agents call speechwire_list_judge_types to retrieve information from SpeechWire MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix and naming pattern align with Read category tools that query tournament data. No side effects, modifications, deletions, or financial implications. Confidence is 0.85 rather than higher due to empty description, but the sibling tools and server context (secure access to tournament data queries) provide strong corroborating evidence.
From the tool's definition Tool name 'speechwire_list_judge_types' indicates a retrieval operation ('list') with no destructive language.
Attacks that exploit this kind of access
speechwire_list_judge_types. It is categorised as a Read tool in the SpeechWire MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SpeechWire MCP Server MCP server in PolicyLayer and add a rule for speechwire_list_judge_types: 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 SpeechWire MCP Server. Nothing to install.
speechwire_list_judge_types 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 speechwire_list_judge_types 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 speechwire_list_judge_types. 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.
speechwire_list_judge_types is provided by the SpeechWire MCP Server MCP server (jessica-writes-code/speechwire-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 →