Reject a pending visitor (not yet implemented)
AI agents use ttya_reject to create or update resources in Networkselfmd — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Networkselfmd environment.
The tool rejects (declines) a pending visitor connection, which is a reversible modification to network state—the visitor could re-request access. This is a Write operation rather than Destructive since rejection is not permanent data deletion and can be undone by accepting a new request.
From the tool's definition Tool name 'ttya_reject' and description 'Reject a pending visitor (not yet implemented)' indicate a state-change operation that modifies visitor/connection status in the P2P network.
Attacks that exploit this kind of access
Reject a pending visitor (not yet implemented). It is categorised as a Write tool in the Networkselfmd MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Networkselfmd MCP server in PolicyLayer and add a rule for ttya_reject: 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 Networkselfmd. Nothing to install.
ttya_reject 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 ttya_reject 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 ttya_reject. 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.
ttya_reject is provided by the Networkselfmd MCP server (selfmd/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 →