Low Risk

analyze_garm

Compute GARM brand safety score for a website or category. Based on the GARM (Global Alliance for Responsible Media) Brand Suitability Framework. Maps content categories to 11 GARM sensitive content categories with risk levels (Floor, High, Medium, Low). Can either: 1. Provide a URL - classificat...

Risk signalsAccepts URL/endpoint input (url)

Part of the Mcp server.

analyze_garm is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP →

Free to start. No card required.

AI agents call analyze_garm to retrieve information from Mcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though analyze_garm only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_garm": {}
  }
}

See the full Mcp policy for all 10 tools.

Get this rule live on your own Mcp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP →

View all 10 tools →

These attack patterns abuse exactly the kind of access analyze_garm gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so analyze_garm only ever does what you allow.

SECURE MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the analyze_garm tool do? +

Compute GARM brand safety score for a website or category. Based on the GARM (Global Alliance for Responsible Media) Brand Suitability Framework. Maps content categories to 11 GARM sensitive content categories with risk levels (Floor, High, Medium, Low). Can either: 1. Provide a URL - classification will be fetched and mapped to GARM 2. Provide category and sentiment directly for instant scoring Score interpretation: higher = safer for advertising. Floor categories (e.g., Adult) always score 0/F regardless of sentiment. Args: category: LLMSE category (e.g., "Adult", "Politics", "Sports"). sentiment: Content sentiment ("Bad", "Neutral", "Good"). url: Optional URL to analyze (fetches classification from cache). Returns: GARM brand safety analysis with: - score: Brand safety score (0-100, higher = safer) - grade: Letter grade (A-F) - garm_category: Matched GARM category name or None - risk_level: "floor"|"high"|"medium"|"low"|"none" - is_floor: True if not suitable for any advertising - issues: Categorized issues {critical, warnings, info} - recommendations: Improvement suggestions. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_garm? +

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

What risk level is analyze_garm? +

analyze_garm is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_garm? +

Yes. Add a rate_limit block to the analyze_garm 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 analyze_garm completely? +

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

analyze_garm is provided by the MCP server (https://llmse.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp tool call.

Deterministic rules across all 10 Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.