polymarket_event_tags
List tags for a Polymarket event. Returns normalized tag rows attached to one Polymarket event id.
This record as markdown: /tools/crawlora-mcp/polymarket-event-tags.md
What polymarket_event_tags does on Crawlora
AI agents call polymarket_event_tags to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Polymarket event id |
Parameters from the server's own tool schema.
Why polymarket_event_tags is rated Low
This tool retrieves and lists tag data associated with a Polymarket event. The use of 'List' and 'Returns' indicates a read-only query operation that retrieves information without creating, modifying, deleting, executing code, or involving financial transactions. The operation has no side effects on the underlying data.
From the tool's definition Tool name 'polymarket_event_tags' and description 'List tags for a Polymarket event. Returns normalized tag rows attached to one Polymarket event id.' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs polymarket_event_tags safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For polymarket_event_tags, this is the rule to start with:
polymarket_event_tags is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every polymarket_event_tags call is checked against it from then on.
Questions about polymarket_event_tags
List tags for a Polymarket event. Returns normalized tag rows attached to one Polymarket event id. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
polymarket_event_tags accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for polymarket_event_tags: 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 Crawlora. Nothing to install.
polymarket_event_tags 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 polymarket_event_tags 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 polymarket_event_tags. 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.
polymarket_event_tags is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue