AI agents call name to retrieve information from Teeshield without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
With an empty description, classification confidence is reduced. However, the minimal tool name 'name' most naturally maps to a Read operation (retrieving/returning a name value) rather than any action with side effects. No evidence suggests Write, Execute, Destructive, or Financial operations. Severity is low because even if misused, a simple name retrieval has minimal blast radius.
From the tool's definition Tool name is 'name' with no description provided. The name suggests a simple retrieval or identification function, likely returning a name or identifier.
Documented attack patterns abuse exactly the kind of access name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teeshield, and nothing reaches the server without passing your rules. This is the rule we recommend for name:
{
"version": "1",
"default": "deny",
"tools": {
"name": {}
}
}name is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
name. It is categorised as a Read tool in the Teeshield MCP Server, which means it retrieves data without modifying state.
Register the Teeshield MCP server in PolicyLayer and add a rule for name: 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 Teeshield. Nothing to install.
name is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the name 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 name. 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.
name is provided by the Teeshield MCP server (teehooai/spidershield). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teeshield, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Teeshield tools catalogued and risk-classified — across an index of 43,000+ MCP servers.