AI agents use tenth_man_configure to create or update resources in Tenth Man — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenth Man environment.
This tool creates or modifies configuration data (preferences, timeouts, trigger patterns) without irreversibly deleting data or executing arbitrary external code. While configuration changes could affect system behavior, they are reversible and do not directly execute operations or move data.
From the tool's definition "Configure agent preferences, timeouts, and trigger patterns" - the tool modifies configuration settings for the review system. The description explicitly indicates it changes preferences and patterns, which are reversible modifications to system state.
Attacks that exploit this kind of access
Configure agent preferences, timeouts, and trigger patterns for the 10th Man Protocol. Auto-detects available CLI agents if not specified. It is categorised as a Write tool in the Tenth Man MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenth Man MCP server in PolicyLayer and add a rule for tenth_man_configure: 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 Tenth Man. Nothing to install.
tenth_man_configure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tenth_man_configure 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.
Set action: deny in the PolicyLayer policy for tenth_man_configure. 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.
tenth_man_configure is provided by the Tenth Man MCP server (keeganthewhi/tenth-man-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →