Start the TTYA web server for visitor interactions (not yet implemented)
AI agents invoke ttya_start to trigger actions in Networkselfmd. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Starting a web server is an Execute action—it runs a process and initiates external operations (listening on ports, accepting connections, exposing endpoints). While not destructive or financial, it can impact system state and network exposure.
From the tool's definition Tool name 'ttya_start' and description 'Start the TTYA web server' indicate execution of a server process.
Attacks that exploit this kind of access
Start the TTYA web server for visitor interactions (not yet implemented). It is categorised as a Execute tool in the Networkselfmd MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Networkselfmd MCP server in PolicyLayer and add a rule for ttya_start: 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_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ttya_start 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_start. 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_start 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 →