Check if user is authenticated with Last.fm - Use this to verify login status before accessing personal music data
AI agents call lastfm_auth_status to retrieve information from Lastfm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks and retrieves authentication status information. It performs no modifications, does not execute code or commands, does not delete data, and does not involve financial transactions. It is a simple status verification read operation with minimal blast radius if misused—an attacker could only learn whether a user is authenticated, not access their data or cause harm.
From the tool's definition Tool name contains 'auth_status' and description states 'Check if user is authenticated' and 'verify login status' - purely informational queries with no side effects.
Documented attack patterns abuse exactly the kind of access lastfm_auth_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lastfm, and nothing reaches the server without passing your rules. This is the rule we recommend for lastfm_auth_status:
{
"version": "1",
"default": "deny",
"tools": {
"lastfm_auth_status": {}
}
}lastfm_auth_status 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.
Check if user is authenticated with Last.fm - Use this to verify login status before accessing personal music data. It is categorised as a Read tool in the Lastfm MCP Server, which means it retrieves data without modifying state.
Register the Lastfm MCP server in PolicyLayer and add a rule for lastfm_auth_status: 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 Lastfm. Nothing to install.
lastfm_auth_status 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 lastfm_auth_status 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 lastfm_auth_status. 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.
lastfm_auth_status is provided by the Lastfm MCP server (rianvdm/lastfm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Lastfm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Lastfm tools catalogued and risk-classified — across an index of 42,500+ MCP servers.