profanity_filter

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/profanity-filter.md

WHAT IT DOES

What profanity_filter does on ScorpTech x402 API

AI agents use profanity_filter to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.

Parameter	Type	Required	Description
`mask`	string	—	partial f*, full **, grawlix #$@!, label [profanity]
`text`	string	Yes	Text to check
`reveal`	boolean	—	Include the matched dictionary word in each hit
`allowWords`	array	—	Words never to flag
`extraWords`	array	—	Extra words to block (moderate)
`minSeverity`	string	—	Ignore hits below this

Parameters from the server's own tool schema.

RISK

Why profanity_filter is rated Medium

An AI agent can call profanity_filter faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs profanity_filter safely

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

profanity_filter Rate-limited

profanity_filter stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "profanity_filter": {
      "limits": [
        {
          "counter": "profanity_filter_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every profanity_filter call is checked against it from then on.

FAQ

Questions about profanity_filter

What does the profanity_filter tool do? +

Profanity, sexual-language and slur filter for chat, usernames, reviews and LLM output: token-level matching (no Scunthorpe false positives) with obfuscation handling (leetspeak f4ck / sh1t, masked letters f*ck, repeated letters fuuuck, separators f.u.c.k / f u c k, accents), inflections and compounds (bullshit, motherf...). Severity mild / moderate / severe and category per hit, masked output in four styles, custom block / allow words. Matched words are never echoed unless reveal is set. Offline, English. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/profanity-filter. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does profanity_filter accept? +

profanity_filter accepts 6 parameters: mask, text, reveal, allowWords, extraWords, minSeverity. Required: text. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on profanity_filter? +

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

What risk level is profanity_filter? +

profanity_filter is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit profanity_filter? +

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

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

profanity_filter is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →