AI agents call entity_info to retrieve information from FastMCP Multi-Tenancy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about an entity without performing side effects, modifications, or state changes. It fits the Read category definition of retrieving data with no side effects. Severity is low because entity information retrieval poses minimal risk unless the entity data itself is highly sensitive, but the tool itself performs no dangerous operations.
From the tool's definition Tool name 'entity_info' and description 'Get information about the current entity' indicate a retrieval operation. The verb 'Get' and the read-only nature of querying entity information without modification, deletion, or execution suggests a read operation.
Documented attack patterns abuse exactly the kind of access entity_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FastMCP Multi-Tenancy, and nothing reaches the server without passing your rules. This is the rule we recommend for entity_info:
{
"version": "1",
"default": "deny",
"tools": {
"entity_info": {}
}
}entity_info 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.
Get information about the current entity. It is categorised as a Read tool in the FastMCP Multi-Tenancy MCP Server, which means it retrieves data without modifying state.
Register the FastMCP Multi-Tenancy MCP server in PolicyLayer and add a rule for entity_info: 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 FastMCP Multi-Tenancy. Nothing to install.
entity_info 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 entity_info 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 entity_info. 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.
entity_info is provided by the FastMCP Multi-Tenancy MCP server (timothywangdev/mcptoolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FastMCP Multi-Tenancy, 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.
4 FastMCP Multi-Tenancy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.