run_safe_analytics

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp

High RISK CLASS

Category Execute

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/run-safe-analytics.md

WHAT IT DOES

What run_safe_analytics does on GleanMark Trademark Search

AI agents invoke run_safe_analytics to trigger actions in GleanMark Trademark Search. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`limit`	integer	—	Maximum number of ranked rows, preview marks, or timeline events to return.
`entity`	string	Yes	What to analyze. Ranking currently supports owners. Count, snapshot, and timeline also support firms and correspondents.
`metric`	string	—	Required for count. Ranking currently supports filings only.
`filters`	object	—
`subject_name`	string	—	Required for count, snapshot, and timeline. Examples: "Ideaya Biosciences", "Goodwin Procter", or "Todd Schneider".
`analysis_type`	string	Yes	Business analytics mode: ranking, count, snapshot, or timeline.

Parameters from the server's own tool schema.

RISK

Why run_safe_analytics is rated High

The tool executes analytics queries against the trademark database. While described as 'constrained' and 'safe' (suggesting read-only analytics), the term 'run' combined with 'query' places this in the Execute category rather than Read, as it triggers computation/query execution whose results depend on arguments.

From the tool's definition 'Run a constrained business-level analytics query' — the word 'Run' indicates execution of a query operation against the underlying data store

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_safe_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GleanMark Trademark Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_safe_analytics, this is the rule to start with:

run_safe_analytics Rate-limited

run_safe_analytics stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_safe_analytics": {
      "limits": [
        {
          "counter": "run_safe_analytics_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GleanMark Trademark Search, apply this rule, and every run_safe_analytics call is checked against it from then on.

FAQ

Questions about run_safe_analytics

What does the run_safe_analytics tool do? +

Run a constrained business-level analytics query without exposing schema details. This is the default fallback for bespoke rankings, counts, snapshots, and timelines across owners, firms, and correspondents. Prefer this before chaining search, summary, or web research tools for aggregate business questions. It is categorised as a Execute tool in the GleanMark Trademark Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does run_safe_analytics accept? +

run_safe_analytics accepts 6 parameters: limit, entity, metric, filters, subject_name, analysis_type. Required: entity, analysis_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_safe_analytics? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for run_safe_analytics: 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 GleanMark Trademark Search. Nothing to install.

What risk level is run_safe_analytics? +

run_safe_analytics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_safe_analytics? +

Yes. Add a rate_limit block to the run_safe_analytics 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.

How do I block run_safe_analytics completely? +

Set action: deny in the PolicyLayer policy for run_safe_analytics. 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.

What MCP server provides run_safe_analytics? +

run_safe_analytics is provided by the GleanMark Trademark Search MCP server (https://gleanmark.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GleanMark Trademark Search, and thousands of servers like it.

This server

All 61 GleanMark Trademark Search tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →