Medium Risk

props_set

Update a specific prop

Part of the Propresenter server.

props_set can modify Propresenter data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE PROPRESENTER →

Free to start. No card required.

AI agents use props_set to create or modify resources in Propresenter. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call props_set repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Propresenter.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "props_set": {
      "limits": [
        {
          "counter": "props_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Propresenter policy for all 177 tools.

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

ENFORCE ON MY PROPRESENTER →

View all 177 tools →

These attack patterns abuse exactly the kind of access props_set 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 props_set only ever does what you allow.

SECURE PROPRESENTER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the props_set tool do? +

Update a specific prop. It is categorised as a Write tool in the Propresenter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on props_set? +

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

What risk level is props_set? +

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

Can I rate-limit props_set? +

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

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

props_set is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Propresenter tool call.

Deterministic rules across all 177 Propresenter 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.