humanize · Filopastry MCP: Risk & Policy

WHAT IT DOES

What humanize does on Filopastry

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

WHY IT NEEDS A POLICY

Why humanize needs a policy

This tool creates or modifies music pattern data reversibly (timing variations can be undone or adjusted further). It does not delete data, execute arbitrary code, transfer funds, or have irreversible effects. The modification is confined to timing parameters within a music composition context, making it a Write operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool performs 'Add human timing variation' to music patterns—modifies existing audio/pattern data by adjusting timing parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

humanize Rate-limited

humanize 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": {
    "humanize": {
      "limits": [
        {
          "counter": "humanize_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Filopastry, so you can run agents against it safely.

FAQ

Questions about humanize

What does the humanize tool do? +

Add human timing variation. It is categorised as a Write tool in the Filopastry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on humanize? +

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

What risk level is humanize? +

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

Can I rate-limit humanize? +

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

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

humanize is provided by the Filopastry MCP server (youwenshao/filopastry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.